Request logs

Fluveo keeps a log of the calls your store makes to the API. Each log shows the request, the answer and how long it took, so you can see what your code sent without adding logging of your own. When a call fails, its error carries request_log_url, a link straight to that call's log.

Where to find it#

Open Settings > Developers > Logs in the Dashboard. The list shows the newest call first. Logs follow the mode you are in: test mode shows the calls made with test keys, live mode the calls made with live keys.

The list does not update by itself. Press Refresh to read it again.

What a log shows#

Each row of the list shows the call's status, its method and path, and its time. Open a row to see the whole log:

A field the call did not have shows as a dash.

Filter the list#

• All, Succeeded and Failed tabs. Succeeded is any 2xx answer, Failed is everything else.
• Filter by path. Type the start of a path, such as /v1/customers, and press Enter.
• Method. GET, POST or DELETE, one at a time.
• Date. A range of whole days.
• More filters. IP address (a whole IPv4 or IPv6 address), Source (API or Dashboard), Error code, such as card_declined, and Resource ID, such as cus_....

What is logged#

Logging never slows down or fails a call. When Fluveo cannot keep a log in time, it skips that one log and the call still gets its normal answer.

What is hidden#

A log is a copy of what your code sent, so Fluveo masks it before it keeps it. Sensitive values are never stored, and nobody can read them back from a log:

A field that is left out is not in the stored body at all; there is no placeholder in its place. Masking changes only the log: the answer your code gets is never changed by it.

Bodies that are not kept#

Some bodies are not stored, and the log says why in one sentence where the body would be:

How long logs are kept#

• A GET call is kept for 31 days.
• A POST or DELETE call is kept for 15 months.

After that the log is deleted and its link opens a message that says it isn't available.

Who can see logs#

Only people who are members of your store and sign in to its Dashboard can read its logs, and only in the mode they are in. There is no API endpoint that reads logs and no API key can open one. A log of another store is never shown, not even with its exact req_... id.

Open a log from an error#

Every error of a logged call carries error.request_log_url, a link to that call's log in the Dashboard:

<store id> is your store's id (mch_...) and <request id> is the answer's own Request-Id header.

• The link is there exactly when the call is logged. An error of a call that is not logged has none, such as a 401 for a missing or unknown key, or a publishable key's secret_key_required.
• A replayed answer, one that comes back with Idempotent-Replayed: true, is a call of its own: its link names its own Request-Id, not the first call's. The first call's id is in its Original-Request header.
• The link is only on the answer. A PaymentIntent's last_payment_error and the events Fluveo sends never carry it.
• A successful answer never carries it. To find a successful call, filter the list by its path or resource id.

Open the link in a browser. If you are signed out, the Dashboard asks you to sign in and then opens the log. It shows the log only when the link is of the store and mode you are in:

Example: a failed call and its log#

1. Send a call that fails#

   Create a PaymentIntent with an amount that is not a whole number. The -i flag prints the answer's headers too.

   cURLCopy

   curl -i https://api.fluveo.com/v1/payment_intents \
     -H "Authorization: Bearer sk_test_..." \
     -d amount=abc \
     -d currency=usd \
     -d "payment_method_types[]=card"

2. Read the error#

   The answer is 400 with a Request-Id header, such as Request-Id: req_8Kd2mPq7XzT4bN. The error names the field at fault and carries request_log_url, whose object is that same id.

   400 Bad RequestCopy

   {
     "error": {
       "code": "parameter_invalid_integer",
       "doc_url": "https://docs.fluveo.com/errors#parameter_invalid_integer",
       "message": "Invalid integer: abc",
       "param": "amount",
       "request_log_url": "https://dash.fluveo.com/mch_.../test/logs?object=req_8Kd2mPq7XzT4bN",
       "type": "invalid_request_error"
     }
   }

3. Open the log#

   Open request_log_url while signed in to the Dashboard in test mode. The log opens with the title POST /v1/payment_intents and a 400 badge. Request ID is req_8Kd2mPq7XzT4bN, Source is API and API key shows Secret key with your key's hint. Error shows type invalid_request_error, code parameter_invalid_integer and parameter amount.

   Request parameters shows what you sent, as JSON. Response body shows the error above, link included.

   Request parametersCopy

   {
     "amount": "abc",
     "currency": "usd",
     "payment_method_types": ["card"]
   }

Fix the amount (2000 is 20.00 in the currency's smallest unit) and send the call again. The new call has its own log, under Succeeded.

Next#

• Errors lists every error and what to do about it.
• Authentication covers keys and the Request-Id header.
• Idempotency explains replayed answers.
• Support says what to send when you need help.