{"id":5171,"date":"2026-11-18T21:19:52","date_gmt":"2026-11-18T21:19:52","guid":{"rendered":"https:\/\/bitflow-solutions.com\/guias-tecnicas\/openapi-3-contract-oauth-client-credentials-api-key\/"},"modified":"2026-11-18T21:19:52","modified_gmt":"2026-11-18T21:19:52","slug":"openapi-3-contract-oauth-client-credentials-api-key","status":"publish","type":"bf_guia","link":"https:\/\/bitflow-solutions.com\/en\/guias-tecnicas\/openapi-3-contract-oauth-client-credentials-api-key\/","title":{"rendered":"OpenAPI 3 contract with OAuth 2.0 Client Credentials and API Key"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A <strong>knowledge guide<\/strong>: what parts an <strong>OpenAPI 3<\/strong> contract has and how to declare in it a very common type of security in enterprise APIs: an <strong>OAuth 2.0 Client Credentials<\/strong> token obtained with a <strong>Client ID and Client Secret<\/strong>, plus an <strong>API Key<\/strong> that identifies the consumer\u2019s subscription. The complete contract and the commands are also in the <strong>README.md<\/strong> on the left.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What you\u2019ll learn<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What parts an OpenAPI 3 contract has and what each one is for.<\/li>\n\n\n<li>How to reuse models, parameters and responses with <code>components<\/code> and <code>$ref<\/code>.<\/li>\n\n\n<li>How security is declared: defining the schemes and requiring them, and the difference between AND and OR.<\/li>\n\n\n<li>How OAuth 2.0 Client Credentials works with a <strong>Client ID and Client Secret<\/strong>.<\/li>\n\n\n<li>What an <strong>API Key<\/strong> adds and why it is combined with the token rather than replacing it.<\/li>\n\n\n<li>How a consumer requests the token and calls the API, and how to validate the contract.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Know the basics of HTTP and REST: methods, headers, status codes and JSON.<\/li>\n\n\n<li>An editor with YAML support, for example Visual Studio Code with an OpenAPI extension.<\/li>\n\n\n<li><strong>Node.js<\/strong>, only to validate the contract in the last step (optional).<\/li>\n\n\n<li>To test it for real: access to an authorisation server (for example, Microsoft Entra ID) with a registered application (optional).<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Step by step<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Understand what a contract is and why to write it first<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">OpenAPI is the standard for describing a REST API in a YAML or JSON file: what paths it has, what each one receives and returns, what errors it gives and how it authenticates. That file is the <strong>contract<\/strong> between whoever publishes the API and whoever consumes it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Writing it before the code (<em>contract first<\/em>) lets frontend, backend and partners work in parallel, generate documentation and clients automatically, validate requests at the API Gateway and detect breaking changes before they are published.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Set up the skeleton of the document<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Field<\/th><th>What it\u2019s for<\/th><\/tr><\/thead><tbody><tr><td><code>openapi<\/code><\/td><td>Version of the specification: 3.0.3 or 3.1.0. Required.<\/td><\/tr><tr><td><code>info<\/code><\/td><td>Title, API version, description and contact. Required.<\/td><\/tr><tr><td><code>servers<\/code><\/td><td>Base URL of each environment (production, pre-production\u2026).<\/td><\/tr><tr><td><code>paths<\/code><\/td><td>The paths and their operations (GET, POST\u2026), with parameters, body and responses.<\/td><\/tr><tr><td><code>components<\/code><\/td><td>Reusable pieces: data schemas, parameters, responses and security schemes.<\/td><\/tr><tr><td><code>security<\/code><\/td><td>The security applied by default to every operation.<\/td><\/tr><tr><td><code>tags<\/code><\/td><td>Group the operations in the documentation.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The minimum skeleton of a valid contract:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openapi: 3.0.3\ninfo:\n  title: Orders API\n  version: 1.0.0\nservers:\n  - url: https:\/\/api.example.com\/orders\/v1\npaths: {}\ncomponents: {}<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">3. Describe the paths and operations<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Each path in <code>paths<\/code> has its operations (get, post\u2026). Give each one a unique <code>operationId<\/code> (code generators use it as the method name) and document all its responses:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>paths:\n  \/orders:\n    get:\n      tags: [Orders]\n      operationId: listOrders\n      summary: Lists the orders\n      responses:\n        '200':\n          description: List of orders\n          content:\n            application\/json:\n              schema:\n                type: array\n                items:\n                  $ref: '#\/components\/schemas\/Order'<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">4. Reuse components<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Anything that repeats is defined once in <code>components<\/code> and referenced with <code>$ref<\/code>. If the order model changes, it changes in every operation at once.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><code>schemas<\/code><\/strong>: the data models (an order, an error), with types, required fields, formats and examples.<\/li>\n\n\n<li><strong><code>parameters<\/code><\/strong>: common parameters, such as pagination.<\/li>\n\n\n<li><strong><code>responses<\/code><\/strong>: repeated responses, such as the 401 and 403 errors.<\/li>\n\n\n<li><strong><code>securitySchemes<\/code><\/strong>: the security mechanisms the API uses.<\/li>\n\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5. Define the security schemes<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">First you <strong>define<\/strong> the mechanisms in <code>components.securitySchemes<\/code>: here, OAuth 2.0 with the Client Credentials flow (with the token URL and the available scopes) and an API Key in a header.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>components:\n  securitySchemes:\n    oauth2:\n      type: oauth2\n      description: OAuth 2.0 Client Credentials (application to application)\n      flows:\n        clientCredentials:\n          tokenUrl: https:\/\/login.example.com\/oauth2\/token\n          scopes:\n            orders.read: Read orders\n            orders.write: Create orders\n    apiKey:\n      type: apiKey\n      in: header\n      name: X-API-Key\n      description: Identifies the consumer's subscription (quotas and analytics)<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">6. Require the security: AND versus OR<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Then you <strong>require<\/strong> them with <code>security<\/code>: at the root of the document, for every operation, or in a specific operation, which then <strong>replaces<\/strong> the root one.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># At the root: every operation requires a token AND an API Key\nsecurity:\n  - oauth2: [orders.read]\n    apiKey: []\n\npaths:\n  \/orders:\n    post:\n      # In an operation: replaces the root one (the API Key must be repeated)\n      security:\n        - oauth2: [orders.write]\n          apiKey: []<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">How you write it decides whether both mechanisms are needed or one is enough:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># AND: token AND API Key (both in the same list item)\nsecurity:\n  - oauth2: [orders.read]\n    apiKey: []\n\n# OR: token OR API Key (each in its own list item)\nsecurity:\n  - oauth2: [orders.read]\n  - apiKey: []<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7. Understand the Client Credentials flow<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It is the flow for communication between applications, with no user involved: a backend, a batch process or a partner\u2019s platform. Each consuming application is registered with the authorisation server and receives two values:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Client ID<\/strong>: identifies the application. It is not secret.<\/li>\n\n\n<li><strong>Client Secret<\/strong>: proves that the application is who it claims to be. It is a password: it never goes in the code, in the contract or in the browser; it is kept in a secrets manager (Azure Key Vault, for example) or in environment variables.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">How it works:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The application requests a token from the <code>tokenUrl<\/code> with its Client ID, its Client Secret and the scopes it needs.<\/li>\n\n\n<li>The authorisation server checks the credentials and returns an <strong>access token<\/strong> with an expiry (for example, one hour).<\/li>\n\n\n<li>The application calls the API with the token in <code>Authorization: Bearer \u2026<\/code>.<\/li>\n\n\n<li>The API Gateway validates the token (signature, expiry, audience and scopes) before letting the request through.<\/li>\n\n\n<li>When the token expires, the application requests another one: this flow has no refresh token.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The token request and its response:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>POST \/oauth2\/token HTTP\/1.1\nHost: login.example.com\nAuthorization: Basic base64(client_id:client_secret)\nContent-Type: application\/x-www-form-urlencoded\n\ngrant_type=client_credentials&amp;scope=orders.read<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>{\n  \"access_token\": \"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...\",\n  \"token_type\": \"Bearer\",\n  \"expires_in\": 3600\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">With Microsoft Entra ID, for example, the <code>tokenUrl<\/code> is <code>https:\/\/login.microsoftonline.com\/{tenant}\/oauth2\/v2.0\/token<\/code> and the scope is requested as <code>api:\/\/{api-id}\/.default<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">8. Understand what the API Key adds<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The API Key identifies the consumer\u2019s <strong>subscription<\/strong>: it is used to apply quotas and rate limits, for usage analytics and to revoke a specific consumer\u2019s access without touching the authorisation server. In Azure API Management, for example, it is the subscription key, which by default travels in the <code>Ocp-Apim-Subscription-Key<\/code> header.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What it doesn\u2019t provide is strong authentication: it is a fixed value, it doesn\u2019t expire on its own and it carries no scopes. That is why it is combined with the token and doesn\u2019t replace it: the token says <strong>who the caller is and what it can do<\/strong>; the API Key, <strong>which subscription it comes in through and with what quota<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9. Document the 401 and 403 errors<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Code<\/th><th>Meaning<\/th><th>Example<\/th><\/tr><\/thead><tbody><tr><td><strong>401<\/strong> Unauthorized<\/td><td>The caller is unknown, or its credentials are not valid.<\/td><td>The token or the API Key is missing, the token has expired or the signature is not valid.<\/td><\/tr><tr><td><strong>403<\/strong> Forbidden<\/td><td>The caller is known, but doesn\u2019t have permission for that operation.<\/td><td>The token only has <code>orders.read<\/code> and tries to create an order.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Documenting them in <code>components.responses<\/code>, with the same error schema, helps the consumer know whether to request a new token (401) or ask for more permissions (403).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">10. Review the complete contract<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An orders API that requires a token and an API Key on every operation, with a read scope by default and a write scope for creating orders. You also have it in the README.md on the left:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openapi: 3.0.3\ninfo:\n  title: Orders API\n  version: 1.0.0\n  description: &gt;\n    Retrieval and creation of orders. Every request needs an OAuth 2.0 token\n    (Client Credentials) and the API Key of the consumer's subscription.\n  contact:\n    name: Integration team\n    email: integration@example.com\nservers:\n  - url: https:\/\/api.example.com\/orders\/v1\n    description: Production\n  - url: https:\/\/api-pre.example.com\/orders\/v1\n    description: Pre-production\n\ntags:\n  - name: Orders\n\nsecurity:\n  - oauth2: [orders.read]\n    apiKey: []\n\npaths:\n  \/orders:\n    get:\n      tags: [Orders]\n      operationId: listOrders\n      summary: Lists the orders\n      parameters:\n        - $ref: '#\/components\/parameters\/Page'\n      responses:\n        '200':\n          description: List of orders\n          content:\n            application\/json:\n              schema:\n                type: array\n                items:\n                  $ref: '#\/components\/schemas\/Order'\n        '401':\n          $ref: '#\/components\/responses\/Unauthenticated'\n        '403':\n          $ref: '#\/components\/responses\/Forbidden'\n    post:\n      tags: [Orders]\n      operationId: createOrder\n      summary: Creates an order\n      security:\n        - oauth2: [orders.write]\n          apiKey: []\n      requestBody:\n        required: true\n        content:\n          application\/json:\n            schema:\n              $ref: '#\/components\/schemas\/NewOrder'\n      responses:\n        '201':\n          description: Order created\n          content:\n            application\/json:\n              schema:\n                $ref: '#\/components\/schemas\/Order'\n        '400':\n          $ref: '#\/components\/responses\/Invalid'\n        '401':\n          $ref: '#\/components\/responses\/Unauthenticated'\n        '403':\n          $ref: '#\/components\/responses\/Forbidden'\n  \/orders\/{orderId}:\n    get:\n      tags: [Orders]\n      operationId: getOrder\n      summary: Retrieves an order\n      parameters:\n        - name: orderId\n          in: path\n          required: true\n          schema:\n            type: string\n      responses:\n        '200':\n          description: The order\n          content:\n            application\/json:\n              schema:\n                $ref: '#\/components\/schemas\/Order'\n        '401':\n          $ref: '#\/components\/responses\/Unauthenticated'\n        '404':\n          description: No order exists with that identifier\n\ncomponents:\n  securitySchemes:\n    oauth2:\n      type: oauth2\n      flows:\n        clientCredentials:\n          tokenUrl: https:\/\/login.example.com\/oauth2\/token\n          scopes:\n            orders.read: Read orders\n            orders.write: Create orders\n    apiKey:\n      type: apiKey\n      in: header\n      name: X-API-Key\n\n  parameters:\n    Page:\n      name: page\n      in: query\n      schema:\n        type: integer\n        minimum: 1\n        default: 1\n\n  schemas:\n    NewOrder:\n      type: object\n      required: [customer, amount]\n      properties:\n        customer:\n          type: string\n          example: CUS-0042\n        amount:\n          type: number\n          format: double\n          minimum: 0\n          example: 129.90\n    Order:\n      allOf:\n        - $ref: '#\/components\/schemas\/NewOrder'\n        - type: object\n          required: [id, status]\n          properties:\n            id:\n              type: string\n              example: ORD-2026-0001\n            status:\n              type: string\n              enum: [pending, shipped, delivered]\n    Error:\n      type: object\n      required: [code, message]\n      properties:\n        code:\n          type: string\n        message:\n          type: string\n\n  responses:\n    Invalid:\n      description: The request does not comply with the contract\n      content:\n        application\/json:\n          schema:\n            $ref: '#\/components\/schemas\/Error'\n    Unauthenticated:\n      description: The token or the API Key is missing or not valid\n      content:\n        application\/json:\n          schema:\n            $ref: '#\/components\/schemas\/Error'\n    Forbidden:\n      description: The token is valid but does not have the required scope\n      content:\n        application\/json:\n          schema:\n            $ref: '#\/components\/schemas\/Error'<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">11. Call the API as a consumer would<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Every call carries both headers:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>GET \/orders\/v1\/orders HTTP\/1.1\nHost: api.example.com\nAuthorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...\nX-API-Key: 3f9c1e...<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">From PowerShell, on Windows, first store the credentials in environment variables (never in the script):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$env:CLIENT_ID     = \"your-client-id\"\n$env:CLIENT_SECRET = \"your-client-secret\"\n$env:API_KEY       = \"your-api-key\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then request the token and call the API:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># 1. Request the token with the Client ID and the Client Secret\n$token = Invoke-RestMethod -Method Post -Uri \"https:\/\/login.example.com\/oauth2\/token\" `\n  -ContentType \"application\/x-www-form-urlencoded\" `\n  -Body @{\n    grant_type    = \"client_credentials\"\n    client_id     = $env:CLIENT_ID\n    client_secret = $env:CLIENT_SECRET\n    scope         = \"orders.read\"\n  }\n\n# 2. Call the API with the token and the API Key\nInvoke-RestMethod -Uri \"https:\/\/api.example.com\/orders\/v1\/orders\" -Headers @{\n  Authorization = \"Bearer $($token.access_token)\"\n  \"X-API-Key\"   = $env:API_KEY\n}<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">12. Validate the contract<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Save the contract as <code>openapi.yaml<\/code> and validate it with Redocly CLI (it needs Node.js). You can also paste it into <code>editor.swagger.io<\/code> to see it as interactive documentation.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>npx @redocly\/cli lint openapi.yaml<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Common errors<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">One mechanism is required when you wanted both (or the other way round)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In <code>security<\/code>, two schemes in the <strong>same<\/strong> list item mean AND; in <strong>different<\/strong> items, OR. Check the hyphens in step 6.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">An operation stops requiring the API Key<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An operation\u2019s <code>security<\/code> completely replaces the root one. If you only put <code>oauth2<\/code> in the operation, the API Key is no longer required: repeat both schemes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The API is left open by mistake<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><code>security: []<\/code> in an operation removes all security. Use it only on purpose, for example on a health endpoint.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets inside the contract<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The contract is shared and published: it never contains a Client Secret or real API Keys, only the <code>tokenUrl<\/code> and the scopes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">A scope is requested that is not declared<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Every scope used in <code>security<\/code> has to exist in <code>flows.clientCredentials.scopes<\/code>; otherwise, validators report an error and the gateway may reject the token.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Error when requesting the token from Microsoft Entra ID<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In Client Credentials, Entra ID only accepts scopes of the form <code>api:\/\/{api-id}\/.default<\/code>: specific permissions are granted to the application as roles, not requested one by one.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">A token is requested on every call<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It overloads the authorisation server and adds latency. Store the token and reuse it until shortly before it expires (<code>expires_in<\/code>).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The API Key travels in the URL<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">As a query parameter (<code>?api_key=\u2026<\/code>) it ends up in proxy and server logs. Always send it in a header.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">401 and 403 are confused<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If a valid token without the required scope returns 401, the consumer will request a new token again and again without solving anything. Lack of permission is 403.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Next steps<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Import the contract into the API Gateway (for example, Azure API Management) and validate the token with its <code>validate-jwt<\/code> policy.<\/li>\n\n\n<li>Generate clients and server stubs from the contract with OpenAPI Generator.<\/li>\n\n\n<li>Spin up a mock server with Prism so that consumers can test before the backend exists.<\/li>\n\n\n<li>Add contract validation and breaking-change detection to the CI\/CD pipeline.<\/li>\n\n\n<li>Version the contract (<code>info.version<\/code> and the <code>\/v1<\/code> path) and don\u2019t publish breaking changes in the same version.<\/li>\n\n<\/ul>\n\n\n","protected":false},"excerpt":{"rendered":"<p>What parts an OpenAPI 3 contract has and how to declare in it security with an OAuth 2.0 token (Client ID and Client Secret) and an API Key, with a complete example contract.<\/p>\n","protected":false},"featured_media":0,"template":"","bf_tecnologia":[101],"bf_nivel":[109],"class_list":["post-5171","bf_guia","type-bf_guia","status-publish","hentry","bf_tecnologia-apis-en","bf_nivel-intermediate"],"acf":[],"_links":{"self":[{"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_guia\/5171","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_guia"}],"about":[{"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/types\/bf_guia"}],"version-history":[{"count":0,"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_guia\/5171\/revisions"}],"wp:attachment":[{"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/media?parent=5171"}],"wp:term":[{"taxonomy":"bf_tecnologia","embeddable":true,"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_tecnologia?post=5171"},{"taxonomy":"bf_nivel","embeddable":true,"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_nivel?post=5171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}