> ## Documentation Index > Fetch the complete documentation index at: https://docs.glassmarkets.io/llms.txt > Use this file to discover all available pages before exploring further. # Get a target's change history > Returns the 100 most recent changes to a target, newest first. It also works for a deleted target you could see. ## OpenAPI ````yaml /openapi.yaml get /v2/organizations/targets/{id}/history/ openapi: 3.0.3 info: title: Glass Market API version: 1.0.0 x-logo: url: https://api.glassmarkets.io/static/black.png backgroundColor: '#FFFFFF' altText: Glass Market API description: > The GlassMarkets API serves the data behind the GlassMarkets app: market data collected from crypto exchanges, and market-making data for the assets your organizations work on. Market makers also use it to submit the metrics they report. The base URL is `https://api.glassmarkets.io`. Requests and responses are JSON, and times are ISO 8601 in UTC. `bps` means basis points: 1 bps is 0.01%. ## Authentication 1. Log in with `POST /v1/login/`, sending your email and password. The response contains a `token` and its `expiry`. 2. Send the token on every request in the `Authorization` header: `Authorization: Token `. A token expires one day after its last use, and at most 30 days after login. With `"remember_me": true` at login, it stays valid for at least 7 days. A request with a missing, expired or revoked token returns `401`: log in again. `POST /v1/logout/` revokes the token. If your account has two-factor authentication, login returns `202` with a `challenge_id`. Send it with your authentication code to `POST /v1/totp/login/` to get the token. ## Quickstart 1. Log in: ``` curl -X POST https://api.glassmarkets.io/v1/login/ \ -H "Content-Type: application/json" \ -d '{"email": "you@example.com", "password": "..."}' ``` 2. List your organizations with `GET /v1/organizations/`. Each organization lists its assets. Each asset lists the exchanges it trades on (`slug`) and the pairs on each exchange. Use these exact values in other requests. ``` curl https://api.glassmarkets.io/v1/organizations/ \ -H "Authorization: Token " ``` 3. Call an endpoint with those values, for example the daily trading volume of one of your assets: ``` curl -G https://api.glassmarkets.io/v2/metrics/volume/ \ -H "Authorization: Token " \ -d assets=BTC -d interval=1d \ -d time_start=2026-09-01T00:00:00Z -d time_end=2026-09-08T00:00:00Z ``` ## Errors Invalid input returns `400` with the problem per field, for example `{"interval": ["This field is required."]}`. Other errors return a status code with a `detail` message: `401` when you are not logged in, `403` when your account may not use the endpoint, and `404` when the resource does not exist. servers: - url: https://api.glassmarkets.io security: [] tags: - name: Authentication description: Log in, log out and read the current session. - name: Organizations description: Your organizations, and the assets, exchanges and pairs each one covers. - name: Reported metrics description: Volume, depth and spread that market makers report for their assets. - name: Trusted metrics description: >- Volume, depth and spread that Shield measures directly from market makers' exchange accounts. - name: Market maker metrics description: >- Market-maker volume, depth, spread, uptime and coverage, combining trusted and reported data. - name: Targets description: >- Market-making targets per asset, exchange and pair, and whether they are met. - name: Market data description: >- Exchange market data for your assets: volume, spread, order book depth, slippage, uptime, futures and more. - name: Leaderboard description: Trading pairs across exchanges, ranked by market data. - name: Loans description: Token loans to market makers for your assets. - name: RFQ description: >- Requests for quotes: a project invites market makers to propose market-making terms for its token. - name: Account description: Manage your password, passkeys and two-factor authentication. paths: /v2/organizations/targets/{id}/history/: get: tags: - Targets summary: Get a target's change history description: >- Returns the 100 most recent changes to a target, newest first. It also works for a deleted target you could see. operationId: v2_organizations_targets_id_history_get parameters: - in: path name: id schema: type: integer required: true responses: '200': content: application/json: schema: type: array items: $ref: '#/components/schemas/OrganizationTargetAuditResponse' description: '' security: - tokenAuth: [] components: schemas: OrganizationTargetAuditResponse: type: object properties: id: type: integer action: $ref: '#/components/schemas/OrganizationTargetAuditResponseActionEnum' actor: allOf: - $ref: '#/components/schemas/OrganizationTargetAuditActorResponse' nullable: true before: nullable: true after: nullable: true changed_fields: type: array items: type: string created_at: type: string format: date-time required: - action - actor - after - before - changed_fields - created_at - id OrganizationTargetAuditResponseActionEnum: enum: - created - updated - deleted type: string description: |- * `created` - Created * `updated` - Updated * `deleted` - Deleted OrganizationTargetAuditActorResponse: type: object properties: id: type: integer username: type: string required: - id - username securitySchemes: tokenAuth: type: apiKey in: header name: Authorization description: >- Token-based authentication with required prefix "Token ". Example: "Token 9944b09199c62bcf9418ad846dd0e4bbdfc6ee4b" x-default: Token ````