Console

The console, at flashpi.com.ec/app, is where you set up and watch your integration. Documents are always issued through the API: the console reads them, but never creates them.

The console is in Spanish by default, with English in the user menu, where you also pick the dark or light theme. Developer terms, such as API key names, event types and error codes, stay in English in both languages.

Signing up and signing in

Sign up at flashpi.com.ec/app/signup with Continue with Google, or an email and password (12 to 128 characters). Google sign-up shows the same terms and privacy notice. Google verifies Gmail and Google Workspace addresses; other addresses still need the verification link we send. For password sign-up, open the link in the same browser, or any browser signed in to that account. Verifying the email turns on the account’s sandbox.
Sign in with Google on the sign-in page. An existing verified account links automatically only when Google is authoritative for the matching address (Gmail or Google Workspace); other addresses need the Flashpi password. Flashpi never changes your account email from Google. An unknown Google account must sign up first. Invitations also offer Google, with the exact invited email.
Two-factor authentication with an authenticator app (TOTP) is mandatory for account owners, whom the console asks to set it up when they first sign in, and optional for members, unless an owner requires it for the whole team. Enrolling gives you ten one-time recovery codes; keep them safe.
Sessions last 12 hours and end after 2 hours without activity.
Sensitive actions, such as creating a live key, uploading a certificate, reading a webhook secret or changing the team, ask you to confirm with your authenticator code (or your password, if you have no authenticator). A Google-only user without an authenticator must enroll one before sensitive actions. A confirmation is valid for 10 minutes. Revoking an API key never asks, so a leaked key can be stopped at once.

Sections

The left menu groups the sections. At the top, under your account, the Test / Live switch chooses the environment of the whole console, since the two are kept apart: the overview, documents, API keys, webhooks and request logs show the chosen environment, and the console keeps it as you move between sections and remembers it for each account. On a phone it is at the top right. Issuers, with each issuer’s certificates, serve both environments. When Flashpi pauses the account’s document emails, a notice above every page says so, with what to do (Paused emails).

Overview

Your sandbox: the demo issuer’s ID, establishment and emission point, today’s test quota with its reset time, a ready-to-run first request in sync mode, a getting-started checklist and your latest test documents. See Sandbox and demo issuer. In Live, the overview shows the steps to issue with tax validity and your latest live documents.

Invoicing

Documents: search the documents of an environment by issuer, type, status, issue dates, counterparty identification or access key, read each one with its tax, RIDE and email statuses (with a notice when the recipient’s address looks mistyped) and its SRI messages, and download its XML and RIDE.
Issuers: add an issuer from its electronic signature (.p12) with New issuer: Flashpi reads the RUC and the holder, and then you review and complete its tax profile (see Create an issuer from its certificate). Then manage its profile, establishments, emission points and brand color. In each issuer’s Certificates tab you renew its .p12, which serves test and live, and follow its verification, validity and revocation checks, with a warning when a certificate is pending, blocked, revoked or about to expire. See Certificates. The shared demo issuer appears here read only.

Developers

API keys: create test and live keys with their name, scope, access level and IP allowlist, see when each was last used, change the name and the allowlist, and revoke them. The whole key is shown only once. See Authentication and API keys.
Webhooks: add endpoints, choose their events and payload mode, read or rotate the signing secret, start a new handshake, and browse the delivery log with every attempt, with manual replays. See Webhooks.
Request logs: every request made with your keys over the last 30 days, with its method, path, status, latency, key, client IP (as the IP allowlists see it), request ID and error code. Bodies are never recorded, and the path is kept without its query string. Filter by status class, method, key or request ID to find a failing integration.

Account

Team: invite people by email as owners or members. A member gets a scope (every issuer, or a list of issuers) and an access level (read only, or read and write), like an API key. Several owners are allowed; the last owner cannot leave.
Settings: your profile, the connected Google account and the language of the emails we send you, your password (or a link to create one by email), two-factor authentication and recovery codes, and the account’s name and RIDE template (modern, classic or minimal; see RIDE and email).

Who can do what

Action	Owners	Members with every issuer, read and write	Members with some issuers, read and write	Read-only members
Read documents, their XML and RIDE	Yes	Yes	Their issuers	Yes (their issuers, when limited)
Add issuers	Yes	Yes	No	No
Change issuers, upload certificates	Yes	Yes	Their issuers (one certificate per environment)	No
Manage test keys and webhook endpoints	Yes	Yes	No	No
See API keys, webhooks and request logs	Yes	Yes	No	When they reach every issuer
Create and change live keys	Yes	No	No	No
Team and account settings, RIDE template	Yes	No	No	No