> ## Documentation Index > Fetch the complete documentation index at: https://lemlist-docs-watch-list-public-api.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > Retrieves the configuration history of a Signal Agent — each past config version with its active period and stats. # Get Signal Agent configuration history Each entry captures a past configuration version that was active during `[startDate, endDate)`. The current, live configuration stays on the Signal Agent itself and is not part of the history. ## OpenAPI ````yaml get /watchlist/history openapi: 3.0.0 info: title: lemlist API version: 1.0.0 description: >- Welcome to the lemlist Developer Documentation. lemlist is very customizable and open. You'll find on this page all the API and integration you can do with lemlist. # Rate Limit lemlist's API rate limits requests in order to prevent abuse and overload of our services. Rate limits are applied on all routes and per API key performing the request. The rate limits are **20** requests per **2** seconds. The response provides any information you may need about it: | Header | Description | | --- | --- | | Retry-After | The number of seconds in which you can retry | | X-RateLimit-Limit | The maximum requests in that time | | X-RateLimit-Remaining | The number of remaining requests you can make | | X-RateLimit-Reset | The date when the rate limit will reset | _Example of values for the rate limit headers_ ``` json { "Retry-After": 2, "X-RateLimit-Limit": 20, "X-RateLimit-Remaining": 7, "X-RateLimit-Reset" : "Tue Feb 16 2021 09:02:42 GMT+0100 (Central European Standard Time)" } ``` # Definitions ## Team A team is the entity of lemlist that can handle users and billing. ## Credits Credits are the coins a team uses to enrich emails, LinkedIn URLs, etc. via the enrich route. Each enrichment feature needs a certain amount of credits to run. ## User You use a user account to connect to lemlist and send messages via the connected emails or LinkedIn account. ## Campaign A campaign is the entity to automate outreach. A campaign has multiple sequences composed of steps. ## Lead A lead is a person that you try to contact via a campaign. ## Activity An activity is the history of all the steps. ## Unsubscribe An unsubscribe occurs when a person decides they don't want to receive emails from you anymore. # Authentication All API routes use the dedicated subdomain `api.lemlist.com`. lemlist uses API keys to allow access to the API. You can get your lemlist API key at our [integration page](https://app.lemlist.com/settings/integrations). You need to add the `Authorization` header using the `Basic` authentication type. `login:password` **where the login is always empty and the password is the API key**. ⚠️ **Don't forget to add the semicolon (**`:`**) before your API key in curl command.** > To authorize, use this code: ``` shell curl https://api.lemlist.com/api/team \ --user ":YourApiKey" ``` **Make sure to replace** **`YourApiKey`** **with your API key.** # Give feedback If you want to report a bug, ask for data, or share with us a use case, please fill this [form](https://lemlist.typeform.com/to/mfVlkyGf). It will help us centralize your needs! servers: - url: https://api.lemlist.com/api security: - basicAuth: [] paths: /watchlist/history: get: tags: - Signal Agents summary: Get Signal Agent configuration history parameters: - name: watchListId in: query required: true description: Signal Agent id whose history to fetch schema: type: string minLength: 1 example: wl_Example000000001 - name: page in: query required: false description: Page number to retrieve example: '1' schema: type: integer minimum: 1 - name: limit in: query required: false description: 'Number of records to retrieve. Maximum value: 100' schema: type: integer minimum: 1 maximum: 100 example: '50' responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/WatchListApiHistoryResponse' '400': description: Validation error - invalid query parameters content: text/plain: example: page must be a positive integer '401': description: Unauthorized - invalid or missing API key content: text/plain: example: Unauthorized '404': description: Signal Agent not found or access denied content: text/plain: example: WatchList not found or access denied '500': description: Internal server error content: text/plain: example: Internal server error components: schemas: WatchListApiHistoryResponse: type: object properties: data: type: array items: $ref: '#/components/schemas/WatchListConfigHistoryEntry' meta: $ref: '#/components/schemas/WatchListListMeta' WatchListConfigHistoryEntry: type: object description: >- A past configuration version of a Signal Agent, active during [startDate, endDate). properties: _id: type: string description: History entry identifier startDate: type: string description: When this configuration version became active format: date-time endDate: type: string description: When this configuration version was replaced format: date-time createdBy: type: string description: User id that made the change name: type: string description: Signal Agent name at capture time emoji: type: string description: Emoji at capture time type: type: string description: Signal type enum: - companyIsHiring - companyRaisedFunds - recruitmentCampaign - jobChange - newHire - companyEmployeeVisitedMyWebsite - customSignals - competitorConnections - competitorReactions - companyFollowers - technologyChange - linkedinPeopleProfile - linkedinCompanyProfile - mergersAcquisitions - promotion - linkedinKeywords - externalSignalContact - externalSignalCompany - buyingIntent entity: type: string description: Entity kind enum: - contact - company segmentType: type: string description: Segment sourcing enum: - all - list - csv filters: type: array items: $ref: '#/components/schemas/WatchListFilter' signalProcessingType: type: string description: Signal processing type enum: - manual - create_opportunity - push_to_campaign stats: type: object description: Signal/campaign stats computed for the window [startDate, endDate). properties: signalsCount: type: integer description: Number of signals detected in the window campaigns: type: array description: Per-campaign breakdown (push_to_campaign agents only) items: type: object WatchListListMeta: type: object properties: pagination: type: object properties: page: type: integer description: Current page number limit: type: integer description: Number of records per page totalRecords: type: integer description: Total records matching the filter totalPages: type: integer description: Total number of pages WatchListFilter: type: object description: >- A filter narrowing which entities or events a Signal Agent tracks. `in` includes matching values, `out` excludes them. required: - filterId properties: filterId: type: string description: Filter identifier enum: - title - description - location - visitLocation - website - pagesTracked - minVisitDuration - minPageViewed - internalTraffic - linkedinUrls - companyLinkedinUrls - companyNames - companyLocation - companyIndustries - companySizes - maxIdentificationsPerDay - excludedVisitorIps - reactionTypes - linkedinTopics - bomboraTopics - watcherWatchKey - questions - fundraisingMinAmount - fundraisingMaxAmount - fundraisingInvestmentTypes - fundraisingInvestors - technologies - detectionMode - maDealTypes - maMinAmount - persona - externalSignalFieldMapping - externalSignalCustomFieldMapping - seniority - crmListIds - minJobCount - timeframe in: type: array description: Values to include items: type: string out: type: array description: Values to exclude items: type: string securitySchemes: basicAuth: type: http scheme: basic ````