OpenID Connect discovery document
gethttps://api.nsin.ir/.well-known/openid-configuration
No authentication.
Everything an OIDC client needs to configure itself: the issuer, the endpoint URLs, and the response types, grant types, scopes and signing algorithms this provider supports.
Note that authorization_endpoint points at the NSIN panel
(https://panel.nsin.ir/oauth/authorize), not at this API — that step
is a page the user sees, not a request your server makes.
Cacheable for an hour.
Responses
200Discovery document.
Content type: application/json
- issuerstring
- authorization_endpointstring
- token_endpointstring
- userinfo_endpointstring
- jwks_uristring
- revocation_endpointstring
- response_types_supportedarray of string
- response_modes_supportedarray of string
- grant_types_supportedarray of string
- subject_types_supportedarray of string
- code_challenge_methods_supportedarray of string
- token_endpoint_auth_methods_supportedarray of string
- scopes_supportedarray of string
- id_token_signing_alg_values_supportedarray of string
- claims_supportedarray of string
- authorization_response_iss_parameter_supportedboolean
{
"issuer": "https://api.nsin.ir",
"authorization_endpoint": "https://panel.nsin.ir/oauth/authorize",
"token_endpoint": "https://api.nsin.ir/oauth/token",
"userinfo_endpoint": "https://api.nsin.ir/oauth/userinfo",
"jwks_uri": "https://api.nsin.ir/.well-known/jwks.json",
"revocation_endpoint": "https://api.nsin.ir/oauth/revoke",
"response_types_supported": [
"string"
],
"response_modes_supported": [
"string"
],
"grant_types_supported": [
"string"
],
"subject_types_supported": [
"string"
],
"code_challenge_methods_supported": [
"string"
],
"token_endpoint_auth_methods_supported": [
"string"
],
"scopes_supported": [
"string"
],
"id_token_signing_alg_values_supported": [
"string"
],
"claims_supported": [
"string"
],
"authorization_response_iss_parameter_supported": true
}Example request
curl -X GET "https://api.nsin.ir/.well-known/openid-configuration" \
-H "Authorization: Bearer $NSIN_API_KEY"