Create OIDCProvider

posthttps://app.fossa.com/api/oidc/providers

Create a new OIDC Provider. Requires a **premium** subscription; organizations below that tier receive a `403`. If the caller lacks permission to create the provider, the endpoint responds with `401`.

Request body (required) · application/json

object

Responses

201Successfully created OIDC Provider
idintegerrequired

The unique identifier of the OIDC Provider

organizationIdintegerrequired

The ID of the organization this provider belongs to

issuerstringrequired

The issuer URL of the OIDC Provider

scopeenumrequired

The scope level of the OIDC Provider

orgteam
scopeIdintegerrequired

The ID associated with the scope: either the organization ID or the team ID

createdAtstring <date-time>required

When the OIDC Provider was created

updatedAtstring <date-time>required

When the OIDC Provider was last updated

400Bad Request
uuidstring

Unique identifier associated with the error

codeinteger

fossa specific error code

messagestring

message associated with this error

namestring

name of the error

httpStatusCodeinteger

http status code number

401Unauthorized
uuidstring

Unique identifier associated with the error

codeinteger

fossa specific error code

messagestring

message associated with this error

namestring

name of the error

httpStatusCodeinteger

http status code number

403Forbidden — requires a premium subscription.
uuidstring

Unique identifier associated with the error

codeinteger

fossa specific error code

messagestring

message associated with this error

namestring

name of the error

httpStatusCodeinteger

http status code number

500Server Error
uuidstring

Unique identifier associated with the error

codeinteger

fossa specific error code

messagestring

message associated with this error

namestring

name of the error

httpStatusCodeinteger

http status code number

Try this endpoint

Build a request and run it against app.fossa.com.

Bearer

Stored in this browser for 24 hours. Try It uses a docs proxy for CORS and does not store tokens server-side.

POST https://app.fossa.com/api/oidc/providers
curl --request POST \  --url 'https://app.fossa.com/api/oidc/providers' \  --header 'accept: application/json' \  --header 'authorization: Bearer YOUR_API_TOKEN' \  --header 'content-type: application/json' \  --data '{  "issuer": "https://oidc.example.com",  "scope": "team",  "scopeId": 789}'

Real request. Mutating methods can change data.

Click Try It to run a request and see the response here.
Enter a Bearer token before running this request.
application/json