Subscription Plans

The Subscription Plans API allows you to manage subscription plans for your ERP system. This API enables you to create, retrieve, update, and delete subscription plans, providing flexibility for diffe

Get all Plans

POST https://api.myapi.com/v1/pet

Fetches all plans.

Query Parameters

Name
Type
Description

limit

string

Limit the number of subscription plans returned in the response. Useful for pagination.

offset

number

Skip a number of subscription plans before starting to return the results. Useful for pagination

sort_by

string

Sort the subscription plans by a specific field. Common sortable fields include amount, titlee, and createdat. Default sorting is in ascending order

{
    "name": "Wilson",
    "owner": {
        "id": "sha7891bikojbkreuy",
        "name": "Samuel Passet",
    "species": "Dog",}
    "breed": "Golden Retriever",
}

Good to know: This API method was created using the API Method block, it's how you can build out an API method documentation from scratch. Have a play with the block and you'll see you can do some nifty things like add and reorder parameters, document responses, and give your methods detailed descriptions.

Updating a pet

Update an existing pet

put
/pet
Required scopes
This endpoint requires the following scopes:
  • : read your pets
  • : modify pets in your account
Authorizations
OAuth2implicitRequired
Authorization URL:
Body
idinteger · int64Optional
namestringRequiredExample: doggie
photoUrlsstring[]Required
statusstring · enumOptional

pet status in the store

Possible values:
Responses
400

Invalid ID supplied

No content

put
/pet
PUT /v2/pet HTTP/1.1
Host: petstore.swagger.io
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 132

{
  "id": 1,
  "category": {
    "id": 1,
    "name": "text"
  },
  "name": "doggie",
  "photoUrls": [
    "text"
  ],
  "tags": [
    {
      "id": 1,
      "name": "text"
    }
  ],
  "status": "available"
}

No content

Good to know: This API method was auto-generated from an example Swagger file. You'll see that it's not editable – that's because the contents are synced to a URL! Any time the linked file changes, the documentation will change too.

Create a new user

POST /users

<Description of the endpoint>

Headers

Name
Value

Content-Type

application/json

Authorization

Bearer <token>

Body

Name
Type
Description

name

string

Name of the user

age

number

Age of the user

Response

{
  "id": 1,
  "name": "John",
  "age": 30
}

Last updated