Cvent Social Tables · Authentication Profile
Cvent Social Tables Authentication
Authentication
Cvent Social Tables secures its APIs with apiKey and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).
3D DesignCateringDiagrammingEvent DesignEvent ManagementEventFloor PlansHospitalityHotelMeetingsSeatingSeating ChartsVenues
Methods: apiKey, oauth2
Schemes: 3
OAuth flows: authorizationCode
API key in: header
Security Schemes
oauth2 oauth2
· flows: authorizationCode
user_token apiKey
· in: header (user_token)
partner_token apiKey
· in: header (partner_token)
Source
Authentication Profile
generated: '2026-09-07'
method: searched
source: https://developer.socialtables.com/docs/authentication/ (OAuth authorization-code flow, read 2026-09-07)
and https://developer.socialtables.com/docs/apps/tutorial; scheme detail derived from openapi/_original/cvent-social-tables-openapi.json
summary:
types:
- apiKey
- oauth2
api_key_in:
- header
oauth2_flows:
- authorizationCode
schemes:
- name: oauth2
type: oauth2
flows:
- flow: authorizationCode
authorizationUrl: https://auth.socialtables.com/oauth/authorize
tokenUrl: https://auth.socialtables.com/oauth/token
scopes: 3
description: OAuth
sources:
- openapi/cvent-social-tables-authentication-api-openapi.yml
- openapi/cvent-social-tables-diagram-favorites-api-openapi.yml
- openapi/cvent-social-tables-diagram-layouts-api-openapi.yml
- openapi/cvent-social-tables-diagram-template-presets-api-openapi.yml
- openapi/cvent-social-tables-diagrams-api-openapi.yml
- openapi/cvent-social-tables-events-api-openapi.yml
- openapi/cvent-social-tables-guest-checkin-api-openapi.yml
- openapi/cvent-social-tables-guest-groups-api-openapi.yml
- openapi/cvent-social-tables-guest-lists-api-openapi.yml
- openapi/cvent-social-tables-guest-meals-api-openapi.yml
- openapi/cvent-social-tables-guest-tags-api-openapi.yml
- openapi/cvent-social-tables-guests-api-openapi.yml
- openapi/cvent-social-tables-layout-automation-api-openapi.yml
- openapi/cvent-social-tables-properties-api-openapi.yml
- openapi/cvent-social-tables-rooms-api-openapi.yml
- openapi/cvent-social-tables-snc-event-integration-api-openapi.yml
- openapi/cvent-social-tables-users-api-openapi.yml
- name: user_token
type: apiKey
in: header
parameter: user_token
description: Social Tables User Token
sources:
- openapi/cvent-social-tables-authentication-api-openapi.yml
- openapi/cvent-social-tables-diagram-favorites-api-openapi.yml
- openapi/cvent-social-tables-diagram-layouts-api-openapi.yml
- openapi/cvent-social-tables-diagram-template-presets-api-openapi.yml
- openapi/cvent-social-tables-diagrams-api-openapi.yml
- openapi/cvent-social-tables-events-api-openapi.yml
- openapi/cvent-social-tables-guest-checkin-api-openapi.yml
- openapi/cvent-social-tables-guest-groups-api-openapi.yml
- openapi/cvent-social-tables-guest-lists-api-openapi.yml
- openapi/cvent-social-tables-guest-meals-api-openapi.yml
- openapi/cvent-social-tables-guest-tags-api-openapi.yml
- openapi/cvent-social-tables-guests-api-openapi.yml
- openapi/cvent-social-tables-layout-automation-api-openapi.yml
- openapi/cvent-social-tables-properties-api-openapi.yml
- openapi/cvent-social-tables-rooms-api-openapi.yml
- openapi/cvent-social-tables-snc-event-integration-api-openapi.yml
- openapi/cvent-social-tables-users-api-openapi.yml
- name: partner_token
type: apiKey
in: header
parameter: partner_token
description: Social Tables Partner Token
sources:
- openapi/cvent-social-tables-authentication-api-openapi.yml
- openapi/cvent-social-tables-diagram-favorites-api-openapi.yml
- openapi/cvent-social-tables-diagram-layouts-api-openapi.yml
- openapi/cvent-social-tables-diagram-template-presets-api-openapi.yml
- openapi/cvent-social-tables-diagrams-api-openapi.yml
- openapi/cvent-social-tables-events-api-openapi.yml
- openapi/cvent-social-tables-guest-checkin-api-openapi.yml
- openapi/cvent-social-tables-guest-groups-api-openapi.yml
- openapi/cvent-social-tables-guest-lists-api-openapi.yml
- openapi/cvent-social-tables-guest-meals-api-openapi.yml
- openapi/cvent-social-tables-guest-tags-api-openapi.yml
- openapi/cvent-social-tables-guests-api-openapi.yml
- openapi/cvent-social-tables-layout-automation-api-openapi.yml
- openapi/cvent-social-tables-properties-api-openapi.yml
- openapi/cvent-social-tables-rooms-api-openapi.yml
- openapi/cvent-social-tables-snc-event-integration-api-openapi.yml
- openapi/cvent-social-tables-users-api-openapi.yml
docs: https://developer.socialtables.com/docs/authentication/
flow_documented:
grant: authorization_code
authorize: https://auth.socialtables.com/oauth/authorize
token: https://api.socialtables.com/4.0/oauth/token (the docs tutorial also shows https://api.socialtables.com/oauth/token;
securityDefinitions names https://auth.socialtables.com/oauth/token)
authorize_params:
- client_id
- redirect_uri
- response_type=code
token_params:
- code
- client_id
- client_secret
- grant_type=authorization_code
- response_type=token
call_header: 'Authorization: Bearer <access_token>'
registration: Apps are created on https://developer.socialtables.com; the redirect URI must be pre-registered.
introspection: GET /4.0/oauth/token returns the identity behind the token, including id and legacy_id.
pkce: false
refresh_token_documented: false
note: The docs and the contract disagree on the token endpoint host — the tutorial posts to api.socialtables.com
while securityDefinitions names auth.socialtables.com. Recorded as published; not resolved here because
both are the provider's own statements.
permissions:
model: role-based, per account / team / entity
docs: https://developer.socialtables.com/docs/api-usage/permissions.html
note: A 401 can mean "not permitted" rather than "not authenticated".
token_types_note: Two apiKey header schemes also exist in the contract — user_token and partner_token
(plus stUserToken / stPartnerToken header parameters on some legacy operations). Neither is explained
anywhere in the public documentation; only the OAuth flow is documented.
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/cvent-social-tables-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.