> ## Documentation Index > Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a partner > Creates a new partner. ## OpenAPI ````yaml /openapi.json post /v0/partners openapi: 3.1.0 info: title: Let's Do This API version: 0.1.0 description: > The full reference — getting started, pagination, error responses, rate limits and the changelog — lives at [partner-help.letsdothis.com/api-reference](https://partner-help.letsdothis.com/api-reference/overview). This page is the interactive OpenAPI view of the same specification. # Authentication Create an API key from **Settings** → **Credentials** in your Let's Do This account and send it as a bearer token: ```bash curl --request GET \ --url "https://api.letsdothis.com/v0/participants" \ --header "Authorization: Bearer YOUR-API-KEY" ``` Keep the key secret: it identifies your organization, so do not ship it in a website or native app. If a key is exposed, revoke it from the same section and create a replacement. # OpenAPI schema Download the [OpenAPI schema](https://api.letsdothis.com/documentation/json) to use with Postman or an OpenAPI client generator. servers: - url: https://api.letsdothis.com description: Production - url: https://api.staging.letsdothis.com description: Staging security: - bearerAuth: [] tags: - name: Events x-group: Events description: Events that participants can register for. - name: EventOccurrences x-group: Event occurrences description: >- Event occurrences scoped to the organizer associated with your Public API credentials. Unlike the public Events catalog, results are limited to your own events. - name: Races x-group: Races description: >- Races within an event occurrence. An event occurrence may have one or more races, for example a 5K and a 10K within the same race day. - name: Tickets x-group: Tickets description: Tickets that are available for events. - name: BookingForms x-group: Booking forms description: >- Booking forms define the questions a booker answers when registering for a ticket. A ticket usually references a single booking form, so expect zero or one, while a booking form may be shared across multiple tickets. - name: BookingFormFields x-group: Booking form fields description: >- Booking form fields are the individual questions on a booking form — their type, label, options, and whether an answer is required. A field can be reused across multiple forms. - name: Bookings x-group: Bookings description: >- Bookings are the transaction record for a registration. A booking may contain one or more participants (entries). - name: Participant x-group: Participants description: Participants are users who successfully booked an event. - name: LineItem x-group: Line items description: Financial details related to individual items within transactions. - name: AddOns x-group: Add-ons description: >- Organizer-owned products that can be purchased and allocated to participants. Imported products retain stable external identities. - name: DiscountCodes x-group: Discount codes description: >- Discount codes participants enter at checkout to reduce the price of a booking. - name: Credits x-group: Credits description: >- Credits are balances participants can spend at checkout, identified by their email address. - name: Referrals x-group: Referrals description: >- Referral programs, the referrers registered on them, and asynchronous imports of historical referrals. - name: Application x-group: Applications description: >- Applications are created when a user applies for tickets that are set up to require an application process, such as balloted or "Good For Age" entries. - name: Partner x-group: Partners description: >- Partners that were created by the organization who can have Reserved Entries assigned to them. - name: ReservedEntries x-group: Reserved entries description: >- Reserved Entries are entries that are reserved for a partner. After being assigned, the partner can then allocate these entries to participants. - name: Timing x-group: Timing description: >- Timing providers push bib numbers and bib-pack shipments back to Let's Do This for the startlist entries they received. Available to select timing partners only. paths: /v0/partners: post: tags: - Partner summary: Create a partner description: Creates a new partner. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CreatePartnerRequest' responses: '200': description: Default Response content: application/json: schema: $ref: '#/components/schemas/Partner' components: schemas: CreatePartnerRequest: title: CreatePartnerRequest type: object properties: name: type: string description: The name of the partner. minLength: 1 pattern: ^(\S).+$ description: type: string description: The description of the partner. externalIds: $ref: '#/components/schemas/PartnerExternalIds' type: $ref: '#/components/schemas/PartnerType' contacts: type: array items: $ref: '#/components/schemas/PartnerContact' description: The contacts associated with this partner. minItems: 1 defaultMarketing: $ref: '#/components/schemas/PartnerMarketing' specificMarketings: type: array items: $ref: '#/components/schemas/SpecificPartnerMarketing' description: Event specific marketing informations associated with this partner. canCreateSubPartners: type: boolean description: Whether this partner can create sub-partners. required: - name - contacts additionalProperties: false Partner: title: Partner type: object properties: id: type: string description: The unique ID of the partner. name: type: string description: The name of the partner. minLength: 1 pattern: ^(\S).+$ description: type: string description: The description of the partner. externalIds: $ref: '#/components/schemas/PartnerExternalIds' type: $ref: '#/components/schemas/PartnerType' contacts: type: array items: $ref: '#/components/schemas/PartnerContact' description: The contacts associated with this partner. minItems: 1 defaultMarketing: $ref: '#/components/schemas/PartnerMarketing' specificMarketings: type: array items: $ref: '#/components/schemas/SpecificPartnerMarketing' description: Event specific marketing informations associated with this partner. canCreateSubPartners: type: boolean description: Whether this partner can create sub-partners. createdAt: $ref: '#/components/schemas/ISODate' updatedAt: $ref: '#/components/schemas/ISODate' required: - id - name - contacts additionalProperties: false description: >- A partner that was created under your organization, eg. a charity or a sponsor. example: id: p_v7k8jsvoj2o name: National Charity description: Donec faucibus augue non pretium pellentesque. type: CHARITY externalIds: national: natId123 enthuse: enth456 contacts: - name: John Doe emailAddress: jd@charity.com defaultMarketing: whyOptIn: Lorem ipsum dolor contactEmailAddress: info@charity.com emailMessage: Nulla sed mi egestas, condimentum orci quis, pulvinar odio emailCtaUrl: http://charity.com/general/info specificMarketings: - value: whyOptIn: Lorem ipsum dolor contactEmailAddress: info@charity.com emailMessage: >- Phasellus laoreet, arcu scelerisque fringilla laoreet, eros ante consequat neque, eu vestibulum odio neque a magna. emailCtaUrl: http://charity.com/event/info eventId: '213131' canCreateSubPartners: false createdAt: '2023-10-14T11:30:00.000Z' updatedAt: '2024-09-14T11:30:00.000Z' PartnerExternalIds: title: PartnerExternalIds type: object properties: national: type: string enthuse: type: string londonMarathon: type: string justGiving: type: string stripe: type: string givestar: type: string runForCharity: type: string goFundraise: type: string additionalProperties: false description: >- External IDs of the partner. These can be configured in the event's settings if needed. PartnerType: title: PartnerType type: string enum: - CHARITY - CORPORATE - FRIENDS_AND_FAMILY - MERCH_PARTNER - SPONSOR PartnerContact: title: PartnerContact type: object properties: name: type: string description: Full name of the contact. minLength: 1 pattern: ^(\S).+$ emailAddress: type: string description: Email address of the contact. format: email required: - name - emailAddress additionalProperties: false description: A contact from the Partner organization. example: name: John Doe emailAddress: jd@charity.com PartnerMarketing: title: PartnerMarketing type: object properties: whyOptIn: type: string description: >- The tagline that will be shown to users. We recommend no more than 50 characters to ensure it displays on smaller devices. emailMessage: type: string description: This appears in the confirmation email sent to participants. emailCtaUrl: type: string description: This link will be visible in the confirmation email. contactEmailAddress: type: string description: The email address that participants can use to contact the Partner. additionalProperties: false description: >- Customize what participants see on the “Charity Opt-In” step on the registration form and on the charity marketing email. SpecificPartnerMarketing: title: SpecificPartnerMarketing type: object properties: value: $ref: '#/components/schemas/PartnerMarketing' eventId: type: string description: The event ID this marketing configuration should apply to. required: - eventId additionalProperties: false description: >- In case you want to use different marketing configuration for specific events. Will override the default configuration. ISODate: title: ISODate type: string description: >- Represents a date and time in ISO 8601 format as a string. The string should follow the format `YYYY-MM-DDTHH:mm:ss.sssZ`, where: - `YYYY`: Four-digit year - `MM`: Two-digit month (01-12) - `DD`: Two-digit day of the month (01-31) - `T`: Delimiter indicating the start of the time component - `HH`: Two-digit hour in 24-hour format (00-23) - `mm`: Two-digit minutes (00-59) - `ss.sss`: Seconds with milliseconds (00.000-59.999) - `Z`: UTC timezone designator **Example:** To represent 11:30 AM on May 8th, 2026, the value would be: `"2026-05-08T11:30:00.000Z"`. example: '2026-05-08T11:30:00.000Z' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ````