Install by platform
PHP and Laravel
Install composer require blipit/blipit
Install the blipit/blipit package (0.3.0 or newer) and call init once with your project's public key. It runs on Blipit's own core and pulls in no other package. Uncaught exceptions, warnings and fatal errors are reported on their own, and Laravel and Symfony are built in.
1Install
composer require blipit/blipit2Initialise at startup
Plain PHP: at the top of your front controller, before any request is handled. Laravel starts Blipit from its config, as in the next step. The key is on the project's Keys page. With an empty key, init writes a warning to the error log and returns false instead of throwing.
use Blipit\Blipit;
Blipit::init([
"key" => "<public key>",
"environment" => "production",
"release" => "myapp@1.4.2",
]);3Get your keys
Sign in at app.blipit.io and open API keys in the sidebar, then your project. Every project has two keys. The public key starts with blipit_pk_: it goes in browser and app code, can only send events, and is safe for anyone to see. The secret key starts with blipit_sk_: it stays on your server or in Odoo, never in a browser, because it can also read and change issues. The secret key is shown only once, right after it is created, so copy it then; if you lose it, press Create a new secret key, and the old one stops working at once. Some SDKs also need the project id, shown on the same page.
4Keep the key in the environment
This SDK sends with the public key. Laravel: add it to .env and to config/services.php; the Blipit service provider is discovered on its own and starts Blipit from that config, so nothing else is needed. Read values through config, because env() returns nothing in app code once the config is cached. Plain PHP: read the key with getenv() from the server's environment.
BLIPIT_KEY=blipit_pk_your_public_key'blipit' => [
'key' => env('BLIPIT_KEY'),
'environment' => env('APP_ENV'),
'release' => env('GIT_SHA'),
],5Keep keys out of git
Keep keys in environment variables or your host's secret settings, never in code you commit, and add your .env files to .gitignore. A public key in a web page is normal. If a secret key ever ends up in git, a public page, a screenshot or a chat, open API keys, press Create a new secret key, and paste the new key wherever the old one was used: the old key stops working straight away.
.env
.env.local
.env.*.local6Laravel and Symfony
Laravel: every exception its handler reports reaches Blipit, so 404s and validation errors stay out. Queries, log lines and HTTP client calls become breadcrumbs, and queued jobs are traced. A Blipit::captureException line you already have in bootstrap/app.php can stay: the same exception is never sent twice. Symfony: register the listener in config/services.yaml and call Blipit::init early in public/index.php and bin/console.
Blipit\Symfony\BlipitListener:
arguments: ['@router']
tags:
- { name: kernel.event_listener, event: kernel.exception, method: onKernelException }
- { name: kernel.event_listener, event: kernel.request, method: onKernelRequest }
- { name: kernel.event_listener, event: kernel.terminate, method: onKernelTerminate }
- { name: kernel.event_listener, event: console.error, method: onConsoleError }7Manual capture and login attempts
Login attempts need the secret key: on the server, init with the secret key instead of the public one, or ingest refuses them with 403 security_needs_secret_key. Scale plan.
Blipit::captureException($e);
Blipit::captureMessage("cache miss rate above 50%", "warning");
Blipit::setUser(["id" => "42", "email" => "ana@example.com"]);
Blipit::captureSecurity("login_failed", $email, "bad_password", null, $request->ip(), $request->userAgent());8Check it works
Open Issues in app.blipit.io. The first event appears within a few seconds, grouped into an issue, and the people in charge get an email.
Blipit::captureMessage("Hello from PHP");Good to know
- Pass "traces_sample_rate" => 0.2 in init and requests show up on the Pulse page. Blipit::trace("import orders", fn () => $importer->run()) times any block inside a traced request or job.
- Upgrading from 0.2: project is no longer needed (it is still accepted), Blipit::dsn() and Blipit::notice() are gone, and before_send now receives and returns the event as an array in Blipit's format.
- Keeping Blipit up to date: the Keeping Blipit up to date guide (docs.blipit.io/updates) explains the update banner, the emails for important releases, the notice in your development console and the update command for this platform.
- One project per app and platform: each project picks its platform when it is created (Android, iOS, React Native, Flutter, Web, Backend or Odoo), and Blipit refuses data from any other platform with a clear error, so an iOS app and an Android app need two projects with two keys. Releases, versions, crash rates and store builds differ per platform, so mixing them in one project makes all of them wrong. A Web project also takes the server side of the same web app (the Next.js server or Node), and a React Native or Flutter project also takes its own native Android and iOS crash reports.
Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.

