API Partner Onboarding - S-E-T-T — Sport & Events Tours & Travel

1Company

Who are you? Who receives the invoice?

Company name *

Website *

Country *

VAT number

Billing address *

Company registration number (optional)

Existing S-E-T-T customer no. (optional)

2Contacts

Business and technical contact — plus a dedicated email for API communication.

Business contact

Name *

Position *

Email *

Phone *

Technical contact

Name *

Position *

Email *

Phone *

Technical email for API communication *

3Ticket shop / technical environment

How is your shop built? What can it do today?

URL of your ticket shop *

Which ticket shop system are you using? *

Other (if selected above)

Is there a staging/test environment? *

Yes No In preparation

Staging URL (if available)

Backend technology *

Backend tech: other

Can your system consume REST APIs? *

Yes No Not sure

4Requested API scope

Which API operations do you need? When live?

API operations (choose at least 1) *

Event catalog Listings Pricing & availability Quote Create reservation Booking confirmation / confirm endpoint Ticket / fulfillment status Receive webhooks Demo / tech evaluation only

Please select at least one operation.

Desired start mode *

Sandbox / Test Technical pre-evaluation only Live later Live after technical and commercial approval

5Products / Markets

What do you want to offer and where?

Products (choose at least 1) *

Football Formula 1 Tennis Concerts Hospitality / VIP Cricket Golf Other

Please select at least one product.

Other products (free text)

Target markets / countries *

Expected monthly booking volume *

Expected go-live date *

6Security / Operations

Load profile, IP allowlisting, webhooks, hosting, 24h contact.

Expected requests / minute

Expected requests / day

Do you need IP allowlisting? *

Yes No Not sure

IP addresses (IPv4 / IPv6, one per line)

Do you need webhooks? *

Yes No Later

Webhook endpoint URL (if known)

Hosting provider

Monitoring in place?

Yes No

24h technical contact?

Yes No

Technical emergency contact email *

We accept that only sandbox access will be provided initially. Live bookings are activated only after written approval by S-E-T-T. *

This confirmation is required.

7Business model

Who sells to whom? Who collects payment? Who handles refunds?

You sell to *

Merchant of Record (MoR) *

Who collects payment from the end customer?

Who is responsible for refunds / cancellations? *

Under which brand are tickets sold? *

8End-user data / PII

Which data of your end customers is transferred to SETT? Data protection compliance.

Will end-user data be transferred to S-E-T-T? *

Yes No Not sure

Which data types? (selection)

Name Email Phone Postal address Birth date Passport / ID number Payment data Other

Do you have your end customers' consent to share data with S-E-T-T? *

Yes No Will be added to privacy policy Not applicable

Data protection contact — name

Data protection contact — email *

9Legal

These four confirmations are required for every API partner.

We accept that API credentials must be treated as confidential. We accept that live bookings are activated only after written approval by S-E-T-T. We are ready to sign an NDA / API usage agreement. We confirm that we will not share API credentials with third parties.

All four confirmations are required.

Comment / special requirements (optional)

S-E-T-T Ticket API Partner Onboarding

1Company

2Contacts

Business contact

Technical contact

3Ticket shop / technical environment

4Requested API scope

5Products / Markets

6Security / Operations

7Business model

8End-user data / PII

9Legal