From Bright Pattern Documentation
(Created page with "<translate> = Authorization = The Bright Pattern SMS/MMS API uses basic authentication, OAuth 2.0, which enables secure resources to be retrieved while protecting user credent...") |
(Updated via BpDeleteTranslateTags script) |
||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
− | + | ||
= Authorization = | = Authorization = | ||
− | The Bright Pattern SMS/MMS API uses | + | The Bright Pattern SMS/MMS API uses token authentication. All parameters are URL-encoded. |
− | |||
− | |||
− | |||
− | All parameters are URL-encoded. | ||
For more on authorization, see the ''Tenant Management API Specification'', section [[Tenant-management-api-specification/RequestAccessToken | Request Access Token]]. | For more on authorization, see the ''Tenant Management API Specification'', section [[Tenant-management-api-specification/RequestAccessToken | Request Access Token]]. | ||
− | |||
− | |||
− |
Latest revision as of 04:32, 29 May 2024
Authorization
The Bright Pattern SMS/MMS API uses token authentication. All parameters are URL-encoded.
For more on authorization, see the Tenant Management API Specification, section Request Access Token.