> ## Documentation Index > Fetch the complete documentation index at: https://apidocs.sessionboard.com/llms.txt > Use this file to discover all available pages before exploring further. # Bulk sponsor operations > Create, update, or delete multiple sponsors in a single request (max 100 operations). Requires the `write:sponsors` scope. ## OpenAPI ````yaml /api-reference/openapi.yaml post /v1/event/{eventId}/sponsors/bulk openapi: 3.1.0 info: title: Sessionboard Public API version: '1.0' description: >- REST API for managing sessions, speakers, contacts, sponsors, exhibitors, and event data on the Sessionboard platform. contact: name: Sessionboard Support email: support@sessionboard.com termsOfService: https://www.sessionboard.com/legal/terms-of-service servers: - url: https://public-api.sessionboard.com description: US Region - url: https://public-api-eu.sessionboard.com description: EU Region security: - ApiKey: [] - BearerToken: [] tags: - name: Events description: Manage events on the platform. - name: Sessions description: Search and retrieve sessions within an event. - name: Session Writes description: >- Create, update, delete, and restore sessions. Requires the `write:sessions` scope. - name: Contact Writes description: >- Create, update, delete, and restore contacts. Requires the `write:contacts` scope. - name: Exhibitor Writes description: >- Create, update, delete, and restore exhibitors. Requires the `write:exhibitors` scope. - name: Sponsor Writes description: >- Create, update, delete, and restore sponsors. Requires the `write:sponsors` scope. - name: Field Writes description: >- Create, update, and delete custom fields. Requires the `write:fields` scope. - name: Speakers description: Search and retrieve speakers within an event. - name: Participants description: | Search and retrieve every contact holding a session role on an event — speakers, chairpersons, moderators and custom roles — with the roles each one holds, and list the event's participant roles. - name: Contacts description: Search and retrieve contacts at the organization or event level. - name: Sponsors description: Search and retrieve sponsors within an event. - name: Exhibitors description: Search and retrieve exhibitors within an event. - name: Event Settings description: >- Retrieve event configuration such as fields, tags, tracks, rooms, formats, levels, languages, and session statuses. - name: GDPR description: Manage GDPR data access and erasure requests. - name: Insights description: >- Query event data using SbQL, generate queries with AI, and manage dashboards. - name: Ask description: >- Ask a natural-language question about one event and get a cited answer. Requires the `read:ask` scope, granted explicitly. - name: Metadata Writes description: >- Create, update, and delete session metadata (rooms, tracks, tags, formats, levels, languages, statuses). Requires the `write:metadata` scope. - name: Agenda Planning description: >- Manage agenda drafts, draft sessions, scheduling rules, and evaluation personas. Requires the `write:events` scope. - name: Dashboards & Widgets description: >- Create, read, update, and delete dashboards and widgets at the event or organization level. Requires `write:events` scope for writes. - name: Reports & Queries description: >- Create, read, update, delete, and run saved SbQL queries/reports at the event or organization level. Requires `write:events` scope for writes. - name: Transcriptions description: >- Transcript text on sessions — fragments, summaries, insights, and translations. Requires `read:transcriptions` / `write:transcriptions` scopes. - name: Session Recordings description: >- Session audio files for recording archives (live capture or imported audio). Requires `read:transcriptions` / `write:transcriptions` scopes. - name: Media description: >- Upload video or audio files for automatic transcription. Requires `read:media` / `write:media` scopes. - name: Session Files description: > Documents attached to sessions (PDFs, PowerPoint, Word, images, and similar). Simple upload: `POST .../files/upload` (multipart, max 50 MB). Direct-to-storage: create → PUT → complete (max 500 MB). Requires `read:sessions` / `write:sessions` scopes. See the [Uploading session files](/guides/uploading-session-files) guide. - name: OAuth description: >- OAuth 2.1 endpoints for AI client authorization (Claude, ChatGPT). Mounted at `/oauth/` (not `/v1/`). - name: Log Export description: > Pull your organization's API request, security and audit logs into a SIEM such as Splunk, Microsoft Sentinel or Elastic. Requires a dedicated API token with the `read:audit_logs` scope, which can call nothing else. See the [Exporting logs to a SIEM](/guides/exporting-logs-to-a-siem) guide. - name: Awards description: >- Read and manage Awards programs and their categories, rounds, promo codes, submissions and reviews. Organization-level: paths start at `/v1/organization/{orgId}/awards`. Requires `read:awards` / `write:awards` scopes. - name: Registration description: > Registration inside Sessionboard: registration forms, ticket types, registrations, orders, attendees and check-ins for one event. Requires the preview scopes `read:registrations` / `write:registrations`, which a token or OAuth client gets only when they are named explicitly (not by default, and not listed in `scopes_supported`). The event must have Registration turned on (Early Access); otherwise every endpoint answers `403 FORBIDDEN`. See the [Registration and Expo](/guides/registration-and-expo) guide. - name: Expo description: > Expo floor-map booths and sponsorship inventory for one event. Requires the preview scopes `read:expo` / `write:expo`, which a token or OAuth client gets only when they are named explicitly (not by default, and not listed in `scopes_supported`). The event must have Expo turned on (Early Access); otherwise every endpoint answers `403 FORBIDDEN`. See the [Registration and Expo](/guides/registration-and-expo) guide. paths: /v1/event/{eventId}/sponsors/bulk: post: tags: - Sponsor Writes summary: Bulk sponsor operations description: >- Create, update, or delete multiple sponsors in a single request (max 100 operations). Requires the `write:sponsors` scope. operationId: bulk-sponsors parameters: - name: eventId in: path required: true schema: type: integer description: The event ID. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/BulkOperations' responses: '200': description: Bulk operation completed content: application/json: schema: $ref: '#/components/schemas/BulkResponse' '401': description: Unauthorized '403': description: Missing write:sponsors scope '429': description: Rate limit or daily quota exceeded components: schemas: BulkOperations: type: object description: | Request body for bulk create/update/delete operations. Operations are applied in request order, each in its own transaction, and `results[i]` describes `operations[i]`. A failed operation is rolled back whole and does not stop the ones after it. required: - operations properties: operations: type: array maxItems: 100 description: Array of operations to execute (max 100). items: type: object required: - action properties: action: type: string enum: - create - update - delete description: The operation to perform. id: type: string format: uuid description: Entity ID. Required for `update` and `delete` actions. data: type: object description: > Entity-specific fields. Required for `create` and `update` actions. Session create supports `is_abstract` (boolean, default false). `is_abstract` cannot be changed on update. `data` takes the same fields as the matching single-record create/update endpoint, including `custom_fields` and `translated_fields`. A `translated_fields` entry for a language the event has not enabled fails that operation with `400` and rolls it back — it is no longer accepted and discarded. `custom_fields` is honoured on the contacts, sessions, exhibitors and sponsors bulk endpoints. An unknown `internal_name`, a value of the wrong type, or a field owned by an integration fails **that operation only** — the operations around it in the same batch still commit. **Exception — draft sessions.** `POST /event/{eventId}/agenda-drafts/{draftId}/sessions/bulk` does not accept `custom_fields`, and neither does its single-record sibling. A draft session is a scheduling placement of an existing session inside a draft agenda, not a record of its own, so it has no custom fields to write. Set custom fields on the underlying session through `/event/{eventId}/sessions`. BulkResponse: type: object description: Response body for bulk operations, including per-item results. properties: batch_id: type: string format: uuid description: Unique identifier for this bulk batch. results: type: array description: Per-operation results in the same order as the request. items: type: object properties: index: type: integer description: Zero-based index of the operation in the request array. action: type: string description: The action that was performed (create, update, delete). status: type: string enum: - success - created - associated - updated - deleted - error description: | Whether this individual operation succeeded or failed. Most bulk endpoints report `success` or `error`. The contacts bulk endpoint instead names the outcome: `created`, `associated` (the email already existed in the organization and was linked to this event), `updated`, `deleted`, or `error`. Treat anything other than `error` as a success. id: type: string format: uuid description: The ID of the created or affected entity. error: description: | Error details, present only when `status` is `error`. An object with `code` and `message` on most bulk endpoints. On the contacts bulk endpoint `error` is a plain string and the code is returned alongside it as `error_code`; that difference is longstanding and is kept so existing callers reading the string keep working. oneOf: - type: object properties: code: type: string description: Machine-readable error code. message: type: string description: Human-readable error description. valid_options: type: array items: type: string description: | Present only when `code` is `TYPE_MISMATCH` on a `dropdown` field: every value the field accepts, one array entry per option, in the field's option order. An option label can itself contain a comma (`"Banana, Chocolate"`), so read this array rather than splitting the list in `message`. Absent on every other error. example: code: TYPE_MISMATCH message: >- Field 'product_type' value 'Banana' is not a valid option. Valid options: ["1", "Banana, Chocolate", "Blue, Green, Violet", "10"] valid_options: - '1' - Banana, Chocolate - Blue, Green, Violet - '10' - type: string description: Human-readable error description (contacts bulk). error_code: type: string description: >- Machine-readable error code. Returned by the contacts bulk endpoint alongside the string `error`. summary: type: object description: >- Aggregate counts for the batch. This page previously named the object `stats`; every bulk endpoint has always returned it as `summary`. properties: total: type: integer description: Total number of operations in the batch. succeeded: type: integer description: >- Number of operations that succeeded — every row whose `status` is not `error`, including the contacts bulk endpoint's `created`, `associated`, `updated` and `deleted`. failed: type: integer description: Number of operations that failed. securitySchemes: ApiKey: type: apiKey in: header name: x-access-token description: >- Organization API token. Generate from Organization Settings → API Tokens. BearerToken: type: http scheme: bearer description: >- OAuth 2.1 access token. Obtained via the OAuth PKCE flow at `/oauth/token`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.