Read merchant membership information.

Request

Read merchant membership information. The path is relative to the global /api/v1 prefix.

Authorization

Interactive JWT requests bypass API-token scope metadata, but continue through the normal role, merchant, and permission guards. API tokens are denied on routes without an explicit token policy.

Parameters & body

This route has no path parameters in the published merchant-token contract.

Query parameters are not specified by API.md. Use the feature service contract for filters, pagination, or export options.

Examples

Replace each :parameter segment and provide a server-side environment variable for the bearer credential.

cURL

curl -X GET 'https://api.usevouchify.com/api/v1/memberships/merchant' \
  -H "Authorization: Bearer $VOUCHIFY_TOKEN"

JavaScript

const response = await fetch(
  'https://api.usevouchify.com/api/v1/memberships/merchant',
  {
    method: 'GET',
    headers: {
      Authorization: `Bearer ${process.env.VOUCHIFY_TOKEN}`
    }
  }
);

if (!response.ok) {
  throw new Error(`Vouchify request failed: ${response.status}`);
}

const contentType = response.headers.get('content-type') || '';
const responseBody = await response.text();
const result = responseBody && contentType.includes('application/json')
  ? JSON.parse(responseBody)
  : responseBody || null;

Response contract

API.md states that response bodies are produced by existing feature services; their resource-specific schemas are authoritative. The merchant-token document does not publish a stable success schema or feature-specific error list for this route.