THE 7ZP NETWORKINDEPENDENT TORN PROJECTS

PULSE / CROWDSOURCING

Help me build PULSE.

Help turn public stats into useful history.

I’m building PULSE so Torn players can follow progress over time, not just look at today’s totals. If you’d like to help make it happen, contributing API access is one practical way to support the project.

PULSEPULSEPULSE CROWDSOURCING

What I’m working on

Why contribute?

I want to make it easier to see how things change in Torn: who is making progress, how activity compares, and what happens over time. The plan is to use contributed keys to request selected public statistics about you and other Torn players and build community dashboards on PULSE, run by me through 7ZP.

The permitted categories are public player identity and activity snapshots for population discovery; employment; points bought and sold, trades, auctions and bazaar activity; combat outcomes and money mugged; drugs, overdoses, rehabilitation and consumables; travel, racing, revives, crime and jail activity, bounties, missions and progression; total networth; and public faction membership and ranked-war results. Only fields needed for configured datasets are collected. Historical availability and metric definitions are checked before publication; a complete year of data is not promised.

Dashboard designs are still being developed. The data categories we may collect are disclosed above. Collection uses the Torn API; this permission does not authorise page scraping or in-game actions.

What you’re agreeing to

Before you contribute

This is the scope of your permission today. A Public-access key describes its permissions; the key itself is confidential. Do not post it or send it in a message.

How your API key is used
Data StorageData SharingPurpose of UseKey Storage & SharingKey Access Level
Persistent — stored on 7zp.dev servers. PULSE stores your player ID, encrypted contributed key, consent records, request allowance, retention setting and a hash of your management code. Collected public observations and derived results may remain for the life of PULSE after withdrawal. Data backups exclude contributed keys.Service owners / General public. Contribution records and individual source observations are private to authorised PULSE operators and processes, and to you where applicable. Public dashboards show approved grouped statistics. API keys and management codes are never published. Player-level source records are not publicly released under these terms.Non-malicious statistical analysis / Public community tools. Verify key ownership and permissions; collect the disclosed public Torn statistics about you and other players for grouped dashboards, including background collection while offline. Your selected limit is 15, 30, 45, 60 or 75 requests per rolling minute, including verification and subject to shared account budgets. Existing contributions retain their agreed permissions and allowance. Submitting here does not sign you into Jobs or authorise other services to use your key. Full collection scope.Stored securely / Used only for disclosed PULSE automation. Your key passes through your browser and is sent over HTTPS to PULSE and Torn for verification. PULSE retains it encrypted with no fixed expiry until withdrawal or PULSE closure. Authorised PULSE operators and processes can decrypt it for collection. Retained keys are never supplied to dashboards or their viewers. Torn revocation prevents use; PULSE withdrawal deletes the retained key.Public Only. Verification uses key/info; background collection uses Public-access selections within the linked collection scope. Minimal, Limited, Full and Custom keys are not accepted.

How much of your API allowance?

Choose a maximum of 15, 30, 45, 60 or 75 requests per rolling 60 seconds. The default is 15. This is a limit for your Torn account across all keys supplied to PULSE, including verification and collection; it is not a separate allowance for each key.

Your choice is permission for up to that rate, not a promise of continuous use. Selecting an allowance does not activate collection.

Torn currently documents 100 requests per account per minute across all keys. Other tools share that allowance; PULSE cannot measure all their traffic or reserve the remaining capacity. Choose a limit that leaves room for your other tools. Existing Jobs and OBSIDIAN limits are unchanged. Raising your chosen allowance requires your explicit consent.

If you change your mind

Save the private management code shown after submission. Use it below to check or withdraw your contribution. Withdrawal deletes the stored key and stops new use. A request already sent to Torn may finish. Revoking the key in Torn also prevents further access. Expired contributions cannot be used.

Withdrawing your key stops future use and deletes your contribution record. Previously collected public observations and charts may remain for the life of PULSE; withdrawing a key will not automatically erase that public history. Contact 7ZP about corrections or removal. A material change to purpose, retention, sharing or permissions, or an increase above your agreed request allowance, requires new consent. Collection stores only the selected public observations needed for the configured datasets.

Read Torn’s current official API terms and limits and API documentation. These PULSE contribution options are not Torn requirements or Torn approval of a pooled-key programme. Questions or lost management code? Contact the 7ZP operator without sending your key.

01 / Contribute

Contribute a key

This key is for PULSE only. It won’t be used by Jobs, OBSIDIAN or any other project, and submitting it won’t sign you in anywhere.

Each submission sent for verification makes one ownership and permission check with Torn. A replacement confirmation may require a second submission and check. Your key is cleared from this field afterwards.

Per Torn account, including verification. Other tools share your account allowance.

02 / Your contribution

Manage your contribution

Use your private management code. No shared login and no need to enter your API key again.

Ending this session clears the codes displayed here. It does not withdraw a contribution or sign you out of Jobs or OBSIDIAN.

Getting started

A small part in building PULSE.

  1. Create a key just for PULSE. Choose Public Only in Torn’s API settings. Keep the key private.
  2. Read the terms and contribute a key. One key per player. It is for PULSE alone, not Jobs, OBSIDIAN or another service.
  3. Save your management code. You can check the retention setting or withdraw your key here whenever you want.

Already contributed? Existing 90-day contributions keep their original expiry and remain ineligible for statistics collection. Existing 12-month contributions retain their original expiry unless separately amended with the contributor’s permission. Their disclosed purpose and agreed request allowance remain unchanged; older contributions without a selected allowance remain limited to 10 per minute. To accept this disclosure or change your allowance, submit your key, choose a limit and explicitly confirm replacement. Explicit replacement accepts the new no-fixed-expiry retention and selected request allowance, and invalidates your old management code. Save the new code. Existing contributions are never upgraded automatically.

Jobs API-use disclosure — enrolment addendum jobs-pulse-enrolment-2026-10-08-v2.