FormAssembly · OAuth Scopes
FormAssembly OAuth Scopes
OAuth 2.0
derived
FormAssembly uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
Tokens are issued from https://app.formassembly.com/oauth/access_token.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
FormsData CollectionSalesforceEnterpriseHIPAAComplianceGovernmentFedRAMPWorkflowsE-Signatures
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://app.formassembly.com/oauth/login
https://app.formassembly.com/oauth/login
Token URL
https://app.formassembly.com/oauth/access_token
https://app.formassembly.com/oauth/access_token
Flows
authorizationCode
authorizationCode
Scopes (0)
FormAssembly implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
FormAssembly's OAuth2 API documents an authorization-code flow whose token response includes a scope field, but publishes no named scopes; access tokens are user-based with permissions tied to the authorizing user's account (https://github.com/FormAssembly/formassembly-api).
FormAssembly's OAuth2 API documents an authorization-code flow whose token response includes a scope field, but publishes no named scopes; access tokens are user-based with permissions tied to the authorizing user's account (https://github.com/FormAssembly/formassembly-api).
📄 Provider scope reference: https://github.com/FormAssembly/formassembly-api