> ## Documentation Index > Fetch the complete documentation index at: https://api.tryspecter.com/llms.txt > Use this file to discover all available pages before exploring further. # List API call logs > **What it does** Returns a paginated list of API calls made by your organization, ordered by most recent first. **Why you'd use it** - Audit which endpoints your integration is hitting and how often. - Debug failed calls by inspecting HTTP status codes and paths. - Monitor usage trends across your team's API integrations. ## OpenAPI ````yaml /api-ref/bundle_api.yaml get /logs openapi: 3.0.0 info: title: Specter API termsOfService: https://tryspecter.com/terms/ contact: name: API support email: api-support@tryspecter.com version: 1.0.0 servers: - description: Production url: https://app.tryspecter.com/api/v1 security: - ApiKeyAuth: [] tags: - name: Enrichment description: > Endpoints which can be used to query for data and, if the data is not found request that it be retrieved by Specter systems. - name: Companies description: > Endpoints that provide the most up to date information about all the companies in our data set. Giving the ability to query by a specific company id, or using a keyword such as the domain. This also allows us to enrich the data about a company if we either do not have it or it is older than expected, which means you always have the most up-to-date information possible. - name: People description: > Endpoints that expose Specter people records — profile data and contact details — for a known person ID. - name: Investors description: > Endpoints that expose Specter investor records — profile, activity, targeting, funds, portfolio companies, and the funding rounds they have participated in — for a known investor ID. - name: Talent and Interest Signals description: > Endpoints for retrieving Specter Talent Signals and Investor Interest Signals by ID. - name: News Signals description: > Company-level news signals generated from articles monitored by Specter. Each signal represents a single classified company mention within an article and includes a summary of the newsworthy update (such as funding, deals, revenue, profitability, or traction) along with an assigned importance score. - name: Revenue Signals description: > Revenue and profitability observations for companies, derived from news coverage and public filings. Each signal captures one data point — the revenue or profitability metric, the year it refers to, the source, and the company it is attributed to. - name: Transactions description: > Endpoints that expose transaction detail — funding rounds, acquisitions, and IPOs — by ID. - name: Company Lists description: > Create, query and maintain lists of companies that are of particular interest. The endpoints here allow you to interrogate and maintain those lists using a programmatic interface. - name: People Lists description: > Create, query and maintain lists of people that are of particular interest. The endpoints here allow you to interrogate and maintain those lists using a programmatic interface. - name: Investor Lists description: > Create, query and maintain lists of investors that are of particular interest. The endpoints here allow you to interrogate and maintain those lists using a programmatic interface. - name: Network description: > Endpoints for accessing your team's LinkedIn network - the people and companies your teammates are connected to. - name: Saved Searches description: > Manage searches that have been saved via `tryspecter.com`. These endpoints are useful to programmatically list and delete saved searches. To update a search the UI should be used at `tryspecter.com`. - name: Company Saved Searches description: > Query and get results for company searches that have been saved via `tryspecter.com`. These endpoints are useful to programmatically get results and information for a search. To update a search the UI should be used at `tryspecter.com`. - name: People Saved Searches description: > Query and get results for people searches that have been saved via `tryspecter.com` or via the API. These endpoints are useful to programmatically get results and information for a search. To update a search the UI should be used at `tryspecter.com`. - name: Investor Saved Searches description: > Query and inspect saved investor searches — metadata (name, match counts) and paginated results — from searches saved via `tryspecter.com` or shared with the API. - name: Talent Signals Saved Searches description: > Query and get results for Talent Signals searches that have been saved via `tryspecter.com`. - name: Investor Interest Saved Searches description: > Query and get results for Investor Interest Signals searches that have been saved via `tryspecter.com`. - name: Organization description: > Endpoints for accessing your organization's members and org-level resources. - name: Customer Data description: > Retrieve a log of API calls made by your organization. Useful for auditing usage, debugging integrations, and monitoring activity. paths: /logs: get: tags: - Customer Data summary: List API call logs description: > **What it does** Returns a paginated list of API calls made by your organization, ordered by most recent first. **Why you'd use it** - Audit which endpoints your integration is hitting and how often. - Debug failed calls by inspecting HTTP status codes and paths. - Monitor usage trends across your team's API integrations. parameters: - $ref: '#/components/parameters/PaginationLimit' - $ref: '#/components/parameters/PaginationPage' - $ref: '#/components/parameters/LogsFromParam' - $ref: '#/components/parameters/LogsToParam' responses: '200': description: A paginated list of API log entries. headers: X-Total-Count: schema: type: integer description: Total number of log entries for the organization. Link: schema: type: string description: RFC 5988 pagination links (next, prev, first, last). content: application/json: schema: type: object required: - items - total properties: items: type: array description: The log entries for this page. items: $ref: '#/components/schemas/ApiLogEntry' total: type: integer description: Total number of log entries for the organization. '401': $ref: '#/components/responses/Unauthorized' '402': $ref: '#/components/responses/OutOfCredits' '429': $ref: '#/components/responses/RateLimits' components: parameters: PaginationLimit: in: query name: limit schema: type: number required: false description: The number of results to return, default is 50. PaginationPage: in: query name: page schema: type: number required: false description: The page number of results to return, base 0, default is 0. LogsFromParam: in: query name: from schema: type: string format: date-time required: false description: > Filter logs at or after this datetime (ISO 8601, e.g. `2024-06-01T00:00:00Z`). Granularity up to the minute. LogsToParam: in: query name: to schema: type: string format: date-time required: false description: > Filter logs before or at this datetime (ISO 8601, e.g. `2024-06-30T23:59:00Z`). Granularity up to the minute. schemas: ApiLogEntry: type: object required: - timestamp - path - url - http_method - http_status - status properties: timestamp: type: string format: date-time description: UTC timestamp of the API call. path: type: string description: Request path, e.g. '/v1/companies'. url: type: string description: Full request URL including query string. http_method: type: string description: HTTP method used, e.g. 'GET' or 'POST'. http_status: type: integer description: HTTP status code returned by the API. status: type: string description: Logical status of the call, e.g. 'ok' or 'error'. query: type: object nullable: true description: Query parameters sent with the request, if any. ApiKeyMissing: properties: errorCode: description: API_KEY_MISSING example: API_KEY_MISSING type: string message: description: No API Key was presented on the header X-API-KEY example: No API Key was presented on the header X-API-KEY type: string ApiKeyNotValid: properties: errorCode: description: API_KEY_NOT_VALID example: API_KEY_NOT_VALID type: string message: description: API key present, but not valid example: API key present, but not valid type: string responses: Unauthorized: description: Unauthorized content: application/json: schema: oneOf: - $ref: '#/components/schemas/ApiKeyMissing' - $ref: '#/components/schemas/ApiKeyNotValid' OutOfCredits: description: Out of credits - API credit limit exceeded content: application/json: schema: type: object required: - errorCode - message properties: errorCode: type: string enum: - OUT_OF_CREDITS message: type: string description: | There are no more credits available to complete the request. headers: X-CreditLimit-Limit: schema: type: integer description: The total number of credits allocated for the current period X-CreditLimit-Remaining: schema: type: integer description: The number of credits remaining for the current period X-CreditLimit-Reset: schema: type: number format: float description: The number of seconds until the credit limit resets RateLimits: description: Too Many Requests - API Rate limit exceeded content: application/json: schema: type: object required: - errorCode - message properties: errorCode: type: string description: RATE_LIMITED message: type: string description: You have been rate-limited headers: X-RateLimit-Limit: schema: type: integer description: The total rate limit allowed for this endpoint X-RateLimit-Remaining: schema: type: integer description: The number of requests remaining X-RateLimit-Reset: schema: type: number format: float description: The number of seconds until the rate limit resets securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key ````