openapi: 3.0.0 info: title: VTex Anti-fraud Provider Account Plans API description: ">ℹ️ Onboarding guide\r\n>\r\n> Check the new [Payments onboarding guide](https://developers.vtex.com/docs/guides/payments-overview). We created this guide to improve the onboarding experience for developers at VTEX. It assembles all documentation on our Developer Portal about Payments and is organized by focusing on the developer's journey.\r\n\r\nThe Anti-fraud Provider Protocol is a set of definitions to help you integrate your anti-fraud service API into VTEX platform.\r\n\r\nTo achieve this, you need to implement a web API (REST) following the specifications described in this documentation.\r\n\r\n>⚠️ You can also access our [template on GitHub](https://github.com/vtex-apps/antifraud-provider-example) to help you quickly develop your anti-fraud connector using the Anti-fraud Provider Protocol and VTEX IO.\r\n\r\nTo learn more about the Anti-fraud Provider Protocol, check our [developer guide](https://developers.vtex.com/docs/guides/how-the-integration-protocol-between-vtex-and-antifraud-companies-works).\r\n\r\n## Anti-fraud Provider API Index\r\n\r\n### Anti-fraud Flow\r\n\r\n- `POST` [Send Anti-fraud Pre-Analysis Data (optional)](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#post-/pre-analysis)\r\n- `POST` [Send Anti-fraud Data](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#post-/transactions)\r\n- `PUT` [Update Anti-fraud Transactions (optional)](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#put-/transactions/-transactionId-)\r\n- `GET` [List Anti-fraud Provider Manifest](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#get-/manifest)\r\n- `GET` [Get Anti-fraud Status](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#get-/transactions/-transactions.id-)\r\n- `DELETE` [Stop Anti-fraud Analysis (optional)](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#delete-/transactions/-transactions.Id-)\r\n\r\n### OAuth Flow\r\n\r\n1. `POST` [Retrieve Token](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#post-/authorization/token)\r\n2. `GET` [Redirect](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#get-/redirect)\r\n3. `GET` [Return to VTEX](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#get-/authorizationCode)\r\n4. `GET` [Get Credentials](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol#get-/authorization/credentials)" version: '1.0' servers: - url: https://{providerApiEndpoint} description: Anti-fraud provider endpoint URL. variables: providerApiEndpoint: description: Anti-fraud provider endpoint URL. default: '{providerApiEndpoint}' tags: - name: Plans paths: /api/rns/pvt/plans: get: tags: - Plans summary: VTex List plans description: List plans filtering by some arguments. parameters: - name: periodicity in: query description: Filter plans by available periodicity schema: type: string nullable: true - name: interval in: query description: Filter plans by available interval schema: type: string nullable: true - name: page in: query description: Page used for pagination schema: type: integer format: int32 default: 1 - name: size in: query description: Page size used for pagination schema: type: integer format: int32 default: 15 - name: Content-Type in: header description: Type of the content being sent. required: true style: simple schema: type: string example: application/json - name: Accept in: header description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand. required: true style: simple schema: type: string example: application/json responses: '200': description: Requested plans content: text/plain: schema: type: array items: $ref: '#/components/schemas/StorePlan' application/json: schema: type: array items: $ref: '#/components/schemas/StorePlan' text/json: schema: type: array items: $ref: '#/components/schemas/StorePlan' /api/rns/pvt/plans/{id}: get: tags: - Plans summary: VTex Get plan details description: This endpoint retrieves a specific plan by its ID. parameters: - name: id in: path description: Id from the desired plan required: true schema: type: string nullable: true - name: Content-Type in: header description: Type of the content being sent. required: true style: simple schema: type: string example: application/json - name: Accept in: header description: HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand. required: true style: simple schema: type: string example: application/json responses: '200': description: Requested plan content: text/plain: schema: $ref: '#/components/schemas/StorePlan' application/json: schema: $ref: '#/components/schemas/StorePlan' text/json: schema: $ref: '#/components/schemas/StorePlan' components: schemas: Periodicity: enum: - 0 - 1 - 2 - 3 - 4 type: integer format: int32 Frequency: type: object properties: periodicityAsString: type: string nullable: true periodicity: $ref: '#/components/schemas/Periodicity' interval: type: integer format: int32 additionalProperties: false StorePlan: type: object properties: id: type: string nullable: true frequencies: type: array items: $ref: '#/components/schemas/Frequency' nullable: true additionalProperties: false securitySchemes: VtexIdclientAutCookie: type: apiKey in: header name: VtexIdclientAutCookie description: '[User token](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens), valid for 24 hours.'