See api-docs Menu

Add an Authorization Server Scope

Add a scope to the Authorization Server.











Resource URL

https://<subdomain>/api/2/api_authorizations/:id/scopes

Header Parameters

Authorization

required

string

Set to bearer <access_token>.

Set <access_token> to the access token you generated using the Generate Token API.

The access token must have been generated using an API credential pair created using the scope required to call this API. This API can be called using any one of the following scopes: Manage All.

Content-Type

required

string

Set to application/json.

Resource Parameters

id

required

integer

The id of the authorization server.

Request Parameters

value

required

string

A value representing the api scope that with be authorized

description

required

string

A description of what access the scope enables

Request Body

{
    "value": "custom:scope",
    "description": "A custom scope"
}

Sample Responses

{
    "id": 323005
}

Typically, this error means that your access token value is invalid.

{
    "message": "Unauthorized",
    "statusCode": 401,
    "name": "UnauthorizedError"
}

Invalid API Authorization Server ID

{
    "message": "The resource with the given id could not be found",
    "statusCode": 404,
    "name": "NotFoundError"
}

The scope already exists

{
    "message": "Validation failed: Value has already been taken",
    "statusCode": 422,
    "name": "UnprocessableEntityError"
}

Response Elements

id Unique ID for the Scope

Postman Collection

Replace sample variables indicated by {{ }} with your actual values.

Run in Postman

    Clicking Run in Postman button navigates to the page where you can fork the collection to your workspace. Forking the collection into your workspace will enable you to contribute to the source collection using pull requests. You can also view the collection in a public workspace if you like and even import a copy of the collection using the links present on the screen.

Sample Code

cURL

Replace sample values indicated by < > with your actual values.

Add a Scope

curl 'https://<subdomain>/api/2/scopes' \
-X POST \
-H "Authorization: bearer <access_token>" \ -d '{
    "value": "custom:scope",
    "description": "A custom scope"
}'

Have a Question?

Found a problem or a bug? Submit a support ticket.

Looking for walkthroughs or how-to guides on OneLogin's user and admin features? Check out the documentation in our Knowledge Base.

Have a product idea or request? Share it with us in our Ideas Portal.