> ## Documentation Index > Fetch the complete documentation index at: https://docs.quark.bot/llms.txt > Use this file to discover all available pages before exploring further. # Ignore the next logs about a target > Asks Quark to leave out the next logs about one target: a member, message, channel, role or other thing a log is about. Send it just before, or just after, your bot does something you do not want logged. Active Ignore has to be switched on for the log type, or for every log type, before a request has any effect. A request that is not used expires on its own. A request that leaves out `logType` never covers a protected log type: Ban, Unban, Kick, Timeout and Timeout Removed (39 to 43), every Quark Events log type, Member Leave (2) and Bot Removed (58). To leave one of those out, name it in `logType` and use an Admin token. Requests are recorded in the server's Quark Events channel, as an Ignore Options Updated log that names the token by its ID. A request that names a protected log type is recorded every time. Any other request is recorded once an hour for each token. ## OpenAPI ````yaml /api-reference/openapi.json post /servers/{guild_id}/active/ignore/targets openapi: 3.1.0 info: title: Quark API version: 2.0.0 description: Configure Quark and read your server's logs from your own code. servers: - url: https://quark.bot/api security: - bearerAuth: [] tags: - name: Configuration description: Read the configuration and change server settings. - name: Log channels description: Where each category of log is sent. - name: Logging settings description: Server-wide options and settings for individual log types. - name: Ignore options description: Channels, members, roles and message content left out of the logs. - name: Active Ignore description: Ask Quark not to log something your own bot is about to do. - name: Tags description: Saved messages posted with /tags send. - name: Logs description: Read and export the server's logs. - name: Notifications description: Recent changes to Quark's configuration. - name: Troubleshooting description: Find out why logs are missing, and fix it. - name: Search description: Look up members and channels. - name: Tokens description: List and revoke API tokens. - name: Server description: Reset the server. paths: /servers/{guild_id}/active/ignore/targets: post: tags: - Active Ignore summary: Ignore the next logs about a target description: >- Asks Quark to leave out the next logs about one target: a member, message, channel, role or other thing a log is about. Send it just before, or just after, your bot does something you do not want logged. Active Ignore has to be switched on for the log type, or for every log type, before a request has any effect. A request that is not used expires on its own. A request that leaves out `logType` never covers a protected log type: Ban, Unban, Kick, Timeout and Timeout Removed (39 to 43), every Quark Events log type, Member Leave (2) and Bot Removed (58). To leave one of those out, name it in `logType` and use an Admin token. Requests are recorded in the server's Quark Events channel, as an Ignore Options Updated log that names the token by its ID. A request that names a protected log type is recorded every time. Any other request is recorded once an hour for each token. operationId: activeIgnoreTarget parameters: - $ref: '#/components/parameters/GuildId' - $ref: '#/components/parameters/Bot' requestBody: required: true content: application/json: schema: type: object required: - id - type properties: id: type: string description: The ID of the target. For an invite, its code. type: type: integer enum: - 0 - 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 description: >- What kind of thing `id` is. 0 member, 1 channel, 2 emoji, 3 server, 4 invite, 5 none, 6 message, 7 role, 8 thread, 9 user, 10 stage, 11 event, 12 webhook, 13 sticker. A log matches when it has a target of this kind with this ID. A deleted message, for example, has the message (6) as a target. logType: type: integer minimum: 0 description: >- Only ignore logs of this type. Leave it out to ignore a log of any type that is not protected. Naming a protected log type needs an Admin token. See the log types page. count: type: number exclusiveMinimum: 0 maximum: 100 default: 1 description: >- How many logs to leave out, 100 at most. A fraction is rounded up before the limit is applied. time: type: number exclusiveMinimum: 0 default: 10 description: >- How long the request lasts, in seconds. A fraction is rounded up. Anything over 300 is shortened to 300 (five minutes). example: id: '1290000000000000000' type: 6 logType: 5 responses: '202': description: >- Accepted. The request is stored and Quark leaves out the next matching logs. content: application/json: schema: type: object description: An empty object. example: {} '400': description: >- `guild_id` is not a valid server ID, or the body is invalid: it is not JSON, `id` or `type` is missing or not valid, `logType` is not a whole number, `count` or `time` is not a number above zero, or `count` is over 100. A count over 100 is refused, not shortened, and `error` says so. content: application/json: schema: $ref: '#/components/schemas/Error' '401': $ref: '#/components/responses/Unauthorized' '403': description: >- The token belongs to a different server. Also returned when `logType` is a protected log type and the token is not an Admin token. `error` says so. content: application/json: schema: $ref: '#/components/schemas/Error' '429': $ref: '#/components/responses/RateLimited' components: parameters: GuildId: name: guild_id in: path required: true schema: type: string pattern: ^\d{17,20}$ example: '301655085954367490' description: The server's ID. Must be the server the token was created for. Bot: name: bot in: query required: false schema: type: string enum: - pro description: >- Set to `pro` to act on the Quark Pro bot's configuration. Leave out for the main Quark bot. schemas: Error: type: object properties: error: type: string responses: Unauthorized: description: No token was sent. content: application/json: schema: type: object description: An empty object. example: {} RateLimited: description: Too many requests. Wait for the number of seconds in `Retry-After`. headers: Retry-After: schema: type: integer description: Seconds to wait. X-RateLimit-Limit: schema: type: integer X-RateLimit-Remaining: schema: type: integer content: application/json: schema: type: object description: An empty object. example: {} securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.