C19qrserver API for the COVID-19 Tracking QR Code Signin Server

Name: API for the COVID-19 Tracking QR Code Signin Server API
Brand: COVID-19 QR Code Signin Server API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationapiKey14 EndpointsREST

For Agents

Install Jentic One Beta

Connect the API for the COVID-19 Tracking QR Code Signin Server to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API for the COVID-19 Tracking QR Code Signin Server, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with API for the COVID-19 Tracking QR Code Signin Server API.

Authenticate team members through /login and revoke sessions through /logout

Record QR-code attendee signins by POSTing to /signin

List, retrieve, update, and delete individual signin records by signinId

GET STARTED

Start building with API for the COVID-19 Tracking QR Code Signin Server API

Explore with Jentic

View OpenAPI Document

The COVID-19 QR Code Signin Server API powers a contact-tracing system where attendees check in at venues by scanning a QR code, and team members manage the resulting signin records. It exposes 14 operations covering authentication (login, logout, password change and reset), attendee signin lifecycle (create, list, update, delete), and team member directory management. Authentication is via a token header issued by the login endpoint, and the server is intended to be self-hosted by venue operators rather than offered as a managed service. The spec describes a small open-source project, so endpoint counts and resources are stable but the deployed base URL will be specific to each operator.

Use Cases

Patterns agents use API for the COVID-19 Tracking QR Code Signin Server API for, with concrete tasks.

★ Venue Attendee Check-In

When an attendee scans the venue QR code, the front-end posts the resulting signin payload to /signin and receives a signinId. The venue operator can later query /signins for a date range or fetch /signin/{signinId} for a specific record. This gives small venues a self-hosted contact-tracing log without depending on a national tracing app.

POST a new signin to /signin with the scanned QR payload and store the returned signinId against the attendance log.

Team Member Account Management

Venue managers add front-of-house staff to the system through POST /user, list active accounts through GET /users, and remove staff who leave through DELETE /user/{userId}. Combined with the password reset endpoints this covers the full lifecycle of a team member account on the signin server.

POST a new team member to /user with their email and role, then list /users to confirm the account was created.

Password Reset Flow

When a team member forgets their password, the agent calls /requestPasswordReset to send the reset token, then /verifyPasswordChange to confirm the user's chosen new password meets policy, and finally /changePassword to commit the new credential. This three-step flow keeps the password change auditable on the server.

Call /requestPasswordReset for the user, then /verifyPasswordChange and /changePassword once the user has chosen a new password.

Signin Record Audit and Cleanup

Compliance staff retrieve the full list of signins via GET /signins, inspect specific entries with GET /signin/{signinId}, and remove records via DELETE /signin/{signinId} once the retention window has passed. PUT /signin/{signinId} supports correcting a record without deleting and re-creating it.

GET /signins for the prior month, then DELETE each /signin/{signinId} that is older than the configured retention period.

AI Agent Operator Console via Jentic

Through Jentic, an operator-facing agent searches for an intent like 'log in' or 'list today's signins' and is returned the matching endpoint with its input schema. Because authentication uses a single token header issued by /login, the agent can hold an active session and call any other operation without exposing credentials. Wiring the agent up takes under an hour rather than several days of direct integration work.

Use Jentic search for 'list attendee signins', load the GET /signins schema, and execute it with the active operator token.

Key Endpoints

14 endpoints — the covid-19 qr code signin server api powers a contact-tracing system where attendees check in at venues by scanning a qr code, and team members manage the resulting signin records.

METHOD

PATH

DESCRIPTION

POST

/login

Authenticate a team member and issue a token

POST

/signin

Record a new attendee signin

GET

/signins

List attendee signin records

GET

/signin/{signinId}

Retrieve a specific signin record

DELETE

/signin/{signinId}

Delete a signin record

POST

/user

Create a new team member account

GET

/users

List team member accounts

POST

/changePassword

Commit a password change

POST

/login

Authenticate a team member and issue a token

POST

/signin

Record a new attendee signin

GET

/signins

List attendee signin records

GET

/signin/{signinId}

Retrieve a specific signin record

DELETE

/signin/{signinId}

Delete a signin record

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The token issued by /login is stored once, encrypted, by your own Jentic One instance and injected into the token header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'record an attendee signin' or 'list venue signins', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using API for the COVID-19 Tracking QR Code Signin Server API through Jentic.

What authentication does the COVID-19 QR Signin Server API use?

The API uses an API key passed in the token HTTP header. The token is issued by POST /login and revoked by POST /logout. Through Jentic, the token can be stored in the credential vault so the agent never holds the raw value in its prompt or context.

Can I record an attendee QR-code signin with this API?

Yes. POST the scanned QR payload to /signin to create a new signin record. The response includes the signinId, which can be used later to retrieve, update, or delete the record via /signin/{signinId}.

What are the rate limits for this API?

The OpenAPI specification does not declare rate limits. Because this is a self-hosted contact-tracing server, the operator controls request throughput at their reverse proxy or application layer rather than the API enforcing fixed limits.

How do I list all attendee signins through Jentic?

Run a Jentic search for 'list attendee signins', load the GET /signins schema, and execute it with the active operator token. Install the SDK with pip install jentic and use the async search, load, and execute pattern.

How does the password reset flow work?

It is a three-step flow. Call POST /requestPasswordReset to send a reset token, POST /verifyPasswordChange to confirm the new password meets policy, and POST /changePassword to commit it. Each step has its own endpoint so the flow can be paused for user input between steps.

Is this API free to use?

The signin server is open source and self-hosted, so there is no per-call cost. Operators run their own instance of the server, which means infrastructure cost rather than API pricing applies.

Can I limit what my agent is allowed to do with the COVID-19 QR Signin Server API?

Yes. Because Jentic One is self-hosted, your own rules decide which of the server's operations the agent may call, so you can allow it to record and list signins via POST /signin and GET /signins while withholding destructive calls like DELETE /signin/{signinId} or account creation on POST /user. Since the signin id lives in the URL path (/signin/{signinId}), a rule can pin the agent to reading or updating a specific record rather than the whole log. The /login token is held by your own instance and injected at call time, so the agent only ever exercises the exact operations and credentials you have permitted.

C19qrserver API for the COVID-19 Tracking QR Code Signin Server

Connect the API for the COVID-19 Tracking QR Code Signin Server to your agent

Capabilities

Start building with API for the COVID-19 Tracking QR Code Signin Server API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs