Create Server-Signed Application
POST /auth/apps
Create a new Server-Signed application in the caller's org. This is only required when you must add additional authentication to the request from the server side. We strongly recommend creating a default application unless you have an explicit need for server authentication as this adds additional complexity to the configuration.
User action signature required. See User Action Signing for more information.
Request headers required. See Request Headers for more information.
Authentication required. See Authentication Headers for more information.
Required Permissions
Auth:Apps:Create
Always Required
Auth:Types:Application
Always Required
Request Body
name
*
String
the name of the application, must be unique within the caller's org
relyingPartyId
*
String
the top level domain where the application will be hosted, for example: dfns.io
origin
*
String
the url of the application, for example: https://api.dfns.io
kind
*
String
the kind of application being created, must be ServerSideApplication
publicKey
*
String
the public key that can be used to validate signatures generated by the application
daysValid
Integer
Optional
number of days the application's token will be valid. Default is 730
. Max is 730
permissionId
String
Optional
ID of the permission that will be assigned to the application. If no permission ID is given, the application will be assigned the same permissions as the caller
externalId
String
Optional
user defined value that can be used to correlate the entity with an external system
Example
Responses
See Common Errors for common errors.
See Application Management Errors for application management specific errors.
Success - The newly created application
Last updated