key requests

Request Key

Save a "Get an API key" request and post it to Discord once the response is sent.

A keyless visitor gets 3 per 10 minutes and 10 a day (KEY_REQUEST_LIMIT), on top of the general keyless limit; a keyed caller (a customer, or the acceptance tests) only its key's limits. A request with the hidden website field filled in is a bot: it's acknowledged the same way, so the bot learns nothing, but never saved or posted. A repeat from the same email within an hour is saved but not posted again.

Args: body: The form. background: Runs the Discord post after responding, so the form never waits on Discord. caller: Injected caller, for the form's own per-visitor limit. repo: Injected KeyRequestRepository.

Returns: The acknowledgement.

Raises: HTTPException: 429 (with Retry-After) past the form's limit.

post/key-requests

Request

  • Base URL: https://api.licenscheck.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.licenscheck.com/key-requests
  • Auth: none declared

Request body

namestring required

Who's asking.

emailstring required

Where to send the key.

companystring nullable

Their company, if any.

plan'api' | 'monitoring' | 'volume'

What a "Get an API key" request is for, as chosen on the form.

volume'under_100' | '100_500' | '500_5000' | 'over_5000' required

How many verifications a month the requester expects, as a bucket.

use_casestring required

What they'd check, in their own words.

websitestring

Leave empty. A field hidden from people, which only bots fill in; a filled one is dropped.

Response

Successful Response

receivedboolean required

Always true: the request was accepted.

Changes

No recorded changes to this operation across all 1 revision of this API.