Docs menu

Poshmark API endpoint

Poshmark Categories API

Returns Poshmark's full department/category browse taxonomy (e.g. Women > Shoes, Men > Jackets & Coats). Each entry's path resolves directly against the category endpoint. This is reference data that changes rarely, so responses are cached.

GETapiKey1 credit/requestPoshmarkposhmark.categoriesResponseDoc/poshmark/categories

Endpoint facts

Method: GET
API path: /poshmark/categories
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: Poshmark
Response schema: #/definitions/poshmark.categoriesResponseDoc

Poshmark Scraper API Try Poshmark Categories API in Playground Poshmark API documentation

How this endpoint behaves

No request parameters.

Notable response behavior:

This is reference data that changes rarely, so responses are cached for 24 hours — repeated calls within that window return the cached result rather than re-fetching from Poshmark.
The taxonomy has 2 levels: department, then category. Poshmark's own site navigation shows a further leaf sub-category level for whichever single category is currently being browsed (e.g. Shoes → Sneakers, Heels...), but that level isn't included here — browse into a category via the category endpoint to discover its own sub-categories.
Building the full response requires one fetch per department (6 total). If a department's fetch fails, it's simply omitted from the response rather than failing the whole request — the endpoint only returns an error if every department fails.

Live monitoring

Monitored request: GET /poshmark/categories
Checks passed, 7 days to 14 Oct 2026: 100%
Median response time: 0.34 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /poshmark/categories
Items in departments: 6
Fields filled in every checked item: 4

Field	Filled in, of 6 checked	Values in the sample
id	6
name	6	“Women” and 5 other values
path	6	“Women” and 5 other values
categories	6	median 13 entries

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/poshmark/categories" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "departments": [
      {
        "id": "000e8975d97b4e80ef00a955",
        "name": "Women",
        "path": "Women",
        "categories": [
          {
            "id": "002a8975d97b4e80ef00a955",
            "name": "Accessories",
            "path": "Women-Accessories"
          },
          {
            "id": "00268975d97b4e80ef00a955",
            "name": "Shoes",
            "path": "Women-Shoes"
          }
        ]
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/poshmark.categoriesResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	poshmark.CategoriesResponse	No
data.departments	array	No
data.departments[].categories	array	No
data.departments[].categories[].id	string	No	00268975d97b4e80ef00a955
data.departments[].categories[].name	string	No	Shoes
data.departments[].categories[].path	string	No	Women-Shoes	Path is the exact value the category endpoint's path parameter expects, e.g. "Women-Shoes".
data.departments[].id	string	No	000e8975d97b4e80ef00a955
data.departments[].name	string	No	Women
data.departments[].path	string	No	Women	Path is the exact value the category endpoint's path parameter expects for browsing the department itself, e.g. "Women".
msg	string	No	OK

Failure responses

Status	Description	Schema
500	Internal Server Error	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/poshmark/categories" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More Poshmark endpoint docs Poshmark Scraper API Poshmark brand browse API documentation Poshmark brand directory API documentation Poshmark category browse API documentation Poshmark seller closet (storefront) API documentation Poshmark listing detail API documentation Poshmark search API documentation

Open in Playground Back to group

Docs menu

Poshmark API endpoint

Poshmark Categories API

GETapiKey1 credit/requestPoshmarkposhmark.categoriesResponseDoc/poshmark/categories

Endpoint facts

Method: GET
API path: /poshmark/categories
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: Poshmark
Response schema: #/definitions/poshmark.categoriesResponseDoc

Poshmark Scraper API Try Poshmark Categories API in Playground Poshmark API documentation

How this endpoint behaves

No request parameters.

Notable response behavior:

This is reference data that changes rarely, so responses are cached for 24 hours — repeated calls within that window return the cached result rather than re-fetching from Poshmark.
The taxonomy has 2 levels: department, then category. Poshmark's own site navigation shows a further leaf sub-category level for whichever single category is currently being browsed (e.g. Shoes → Sneakers, Heels...), but that level isn't included here — browse into a category via the category endpoint to discover its own sub-categories.
Building the full response requires one fetch per department (6 total). If a department's fetch fails, it's simply omitted from the response rather than failing the whole request — the endpoint only returns an error if every department fails.

Live monitoring

Monitored request: GET /poshmark/categories
Checks passed, 7 days to 14 Oct 2026: 100%
Median response time: 0.34 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /poshmark/categories
Items in departments: 6
Fields filled in every checked item: 4

Field	Filled in, of 6 checked	Values in the sample
id	6
name	6	“Women” and 5 other values
path	6	“Women” and 5 other values
categories	6	median 13 entries

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/poshmark/categories" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "departments": [
      {
        "id": "000e8975d97b4e80ef00a955",
        "name": "Women",
        "path": "Women",
        "categories": [
          {
            "id": "002a8975d97b4e80ef00a955",
            "name": "Accessories",
            "path": "Women-Accessories"
          },
          {
            "id": "00268975d97b4e80ef00a955",
            "name": "Shoes",
            "path": "Women-Shoes"
          }
        ]
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/poshmark.categoriesResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	poshmark.CategoriesResponse	No
data.departments	array	No
data.departments[].categories	array	No
data.departments[].categories[].id	string	No	00268975d97b4e80ef00a955
data.departments[].categories[].name	string	No	Shoes
data.departments[].categories[].path	string	No	Women-Shoes	Path is the exact value the category endpoint's path parameter expects, e.g. "Women-Shoes".
data.departments[].id	string	No	000e8975d97b4e80ef00a955
data.departments[].name	string	No	Women
data.departments[].path	string	No	Women	Path is the exact value the category endpoint's path parameter expects for browsing the department itself, e.g. "Women".
msg	string	No	OK

Failure responses

Status	Description	Schema
500	Internal Server Error	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/poshmark/categories" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

Open in Playground Back to group

Poshmark Categories API

Endpoint facts

How this endpoint behaves

Live monitoring

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

Poshmark Categories API

Endpoint facts

How this endpoint behaves

Live monitoring

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related