You can connect Optune to your agency website using a ready-made booking display or request form, build a custom show display from public artist data, or discuss an API integration for a more specific workflow.
Choose the approach according to the information you want to show, who should have access and whether another system needs to read data or change it. Custom websites, apps and workflows are separately scoped projects.
Choose an integration approach
What you need | Suitable approach | What to decide |
A straightforward show list on an existing website | A ready-made booking display or embed | The artist or agency scope, appearance and where the embed will be placed. |
A form for promoters to submit new enquiries | Booking Request form | The receiving group, fields, required information and form appearance. |
A show display that is part of your website's own design and content | Custom integration using the artist's public JSON feed | The public fields and layout, event pages and how the website retrieves updates. |
A dashboard, tour-planning tool or connection to another internal system | An API integration | Required data, permissions, read/write operations and responsibility for the integration. |
A complete website with its own admin area | A separately scoped website project | Pages, artist profiles, show pages, forms, content editing, migration and ongoing maintenance. |
Use a standard booking display or request form
The artist and agency integration areas provide the entry points for presenting bookings and configuring request forms. An artist-level display concerns that artist; an agency display has the agency's roster context.
A Booking Request form is for new enquiries. Its wizard lets you configure the information requested and the presentation, then use the generated link or embed code on your website. Review the generated form as a visitor before publishing the website change.
Build a custom public show display
A developer can use the relevant artist's public JSON feed to build the show display directly into your website. The feed contains bookings marked Published. Depending on the public information entered in the booking, the display can use details such as the event name, date, ticket link, ticket status, public event description and flyer.
Rendering the show information as normal website content allows more control over its design, event pages and search-engine presentation. This is a website-development task; it is different from placing a ready-made embed on a page. No integration guarantees search rankings.
If the feed is empty or a show is missing, first check the relevant booking's Published setting. Confirmed and Published are separate: a confirmed private event can remain unpublished.
Use the public feed for public show information. Do not put a private calendar link or private API credential in public website code.
Plan a private API or workflow integration
API integrations can support projects such as a tour dashboard, reporting tool or connection to another business system. The specific data and operations must be checked against the available API and the permissions granted to that integration.
Before implementation, decide:
Which agency or artist data the integration needs.
Whether it only reads data or must also create or update particular records.
Which fields, dates and financial details are required.
Who may see or change the information in the external tool.
How updates, errors and access changes should be handled.
Who will build, operate and maintain the integration.
Use the Optune API documentation when agreeing the technical scope. If your developer has questions after reviewing it, contact the Optune team with the intended workflow. Do not assume that every data type supports every read or write operation.
Can we identify contacts used during a particular period?
Yes. For an agency cleanup project, compare the contacts linked to bookings in the chosen period with the full contact list. Use contact IDs to recognise the same contact across multiple bookings. A contact’s creation or last-change date does not tell you when it was last used in a booking.
Choose the booking period and the agency data to review.
Ask your developer to compare the contact IDs used by those bookings with the contact list.
Review the resulting list before deciding what to retain or remove. Leads, newsletter contacts and other useful records may have no booking in that period.
Agree who will carry out any approved changes and verify the result.
A read-only analysis needs access to the required booking and contact data. Changes or deletions need separate permissions and should be scoped independently. Give your developer the Optune API documentation and keep API keys private.
You can arrange this through your developer, an external CRM project or an individually scoped Optune service. The same analysis does not automatically import, merge or delete contacts. Ongoing synchronisation based on changed records serves a different purpose from identifying historic booking use.
Prepare a useful request for a custom website or integration
Describe the result you want, such as “show each artist's published tour dates on their own page”.
Share the website or system involved and explain who uses it.
List the information that needs to come from Optune and anything that must be written back.
Describe the expected appearance, filters, languages, editing needs and access restrictions, including which information must stay private.
Send the request through Ask for help so that the scope and cost can be discussed.
A complete website project can include a content-management area, artist pages, individual show pages and an adapted request form. Agree these items explicitly. A quote for an embed adjustment is not a quote for a full website rebuild.
What if the project includes Onescreener or a shop?
Agree that scope separately from the Optune show feed or booking form. Pages, content editing, shop products, payments and order documents are distinct project requirements. Describe which of them you need when requesting a proposal; a booking-data integration alone does not establish that the entire shop or website is included.
For a website displaying Optune booking data, Optune recommends a short attribution in the website's legal notice, for example “Booking data provided by Optune” with a link to Optune.
Common questions
Is a custom website included with a standard embed? A custom website, CMS or application is a separate scope. Discuss the required features and cost before development.
Can the website use individual booking fields? Include those fields in the specification. A field being present in Optune does not by itself confirm that it is available in every API, public feed or output.
Can an integration automatically extend or remove provisional bookings? Treat that as a specific workflow to define. Describe its triggers, responses, deadlines and consequences instead of assuming it is part of a standard calendar or poll setup.
Can Optune help build the solution? Contact Optune with the requirements. Custom websites, dashboards and workflow tools can be discussed as individual projects.