> ## 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. # Restore a deleted sponsor > Restore a previously soft-deleted sponsor. Requires the `write:sponsors` scope. Restore has the same reach as the delete it reverses: it restores the **group**, so a group that held both roles comes back as both a sponsor and an exhibitor, and it reappears on every event it was linked to — not only the event in the path. ## OpenAPI ````yaml /api-reference/openapi.yaml post /v1/event/{eventId}/sponsors/{sponsorId}/restore 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/{sponsorId}/restore: post: tags: - Sponsor Writes summary: Restore a deleted sponsor description: > Restore a previously soft-deleted sponsor. Requires the `write:sponsors` scope. Restore has the same reach as the delete it reverses: it restores the **group**, so a group that held both roles comes back as both a sponsor and an exhibitor, and it reappears on every event it was linked to — not only the event in the path. operationId: restore-sponsor parameters: - name: eventId in: path required: true schema: type: integer description: The event ID. - name: sponsorId in: path required: true schema: type: string description: The sponsor ID. responses: '200': description: Sponsor restored content: application/json: schema: $ref: '#/components/schemas/Sponsor' '400': description: > The sponsor is not deleted, so there is nothing to restore. Restore is not idempotent — check before retrying. '401': description: Unauthorized '403': description: Missing write:sponsors scope '404': description: > No sponsor with this id on this event. A record that exists but does not hold the sponsor role — a contact, or a group linked only as the other role — is also a `404` here; look it up on the endpoint for the role it holds. components: schemas: Sponsor: type: object description: A sponsor associated with an event. properties: id: type: string friendly_id: type: string friendly_id_raw: type: integer name: type: string description: type: string logo_image_url: type: string banner_image_url: type: string phone: type: string address_line_1: type: string address_line_2: type: string address_city: type: string address_state: type: string address_postal_code: type: string address_coutnry: type: string description: >- Country (note: field name contains a known typo preserved for backwards compatibility). facebook_url: type: string instagram_url: type: string linkedin_url: type: string snapchat_username: type: string tiktok_username: type: string twitter_url: type: string website_url: type: string created_at: type: string updated_at: type: string custom_fields: type: array items: $ref: '#/components/schemas/CustomFieldValue' translated_fields: type: array items: $ref: '#/components/schemas/TranslatedField' contacts: type: array items: $ref: '#/components/schemas/AccountContact' admin_url: type: string format: uri nullable: true description: Deep link to this entity in the Sessionboard admin UI. examples: - id: b2c3d4e5-f6a7-8901-bcde-f12345678901 friendly_id: SPON-3 friendly_id_raw: 3 name: TechCorp Global description: Platinum sponsor and technology partner. logo_image_url: https://cdn.sessionboard.com/logos/techcorp.png phone: +1-555-0100 address_city: San Francisco address_state: CA address_coutnry: US website_url: https://www.techcorp.example.com linkedin_url: https://www.linkedin.com/company/techcorp created_at: '2024-01-05T08:00:00Z' updated_at: '2024-02-20T12:00:00Z' custom_fields: [] translated_fields: [] contacts: [] CustomFieldValue: type: object description: A custom field value attached to a record. properties: id: type: string name: type: string value: type: - string - boolean - 'null' description: | The formatted field value, or `null` when the field is empty. Numeric field types (`number`, `currency`, `percent`, `quantity`, `formula`) serialize a stored zero as its formatted value (for example `"0"`) — `null` means the field has no value, not that the value is zero. `checkbox` fields serialize as the strings `"Yes"` (checked) and `"No"` (explicitly unchecked); a checkbox that was never set is `null`. Writes take boolean `true` / `false`. `datetime` fields serialize as ISO 8601. On event custom fields (`GET /v1/events?expand=custom_fields`) the value is event-local time with the event's UTC offset (for example `2026-08-15T09:00:00-03:00`), falling back to the raw UTC instant (`2026-08-15T12:00:00.000Z`) when the event has no valid timezone. On session, speaker, sponsor, and exhibitor custom fields the value is the raw UTC instant. `date` (date-only) fields serialize as `M-DD-YYYY`: month without a leading zero, day with one, four-digit year (for example `9-22-2026` for 22 September 2026, `3-04-2026` for 4 March 2026). This is not ISO 8601; parse it with that exact pattern. type: type: string internal_name: type: string created_at: type: string TranslatedField: type: object description: A translated version of a field value. properties: id: type: string name: type: string type: type: string parent_field_id: type: string parent_field_source: type: string parent_field_name: type: string parent_field_internal_name: type: string translated_language: type: string value: type: string AccountContact: type: object description: A contact associated with a sponsor or exhibitor account. properties: id: type: string friendly_id: type: string friendly_id_raw: type: integer full_name: type: string first_name: type: string last_name: type: string email: type: string photo_url: type: string company_name: type: string title: type: string about: type: string is_primary: type: boolean contact_created_at: type: string contact_updated_at: type: string relationship_created_at: type: string relationship_updated_at: type: string 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.