Skip to main content
Portfolios are organization-owned folders of Signa trademark records. Use them to group a client’s marks, attach your own membership references, and request computed deadlines. They do not track matters, tasks, or completion status.

​
Limits

The current configured allowances are: Removing a trademark from your last portfolio that contains it releases its managed-mark slot. Exceeding either allowance returns 409 resource_quota_exceeded, with quota_scope identifying portfolios or managed_marks. Managed marks count on the daily monitoring meter, 1 credit per mark per day, the same meter that mark and portfolio watches use. A mark counts once a day however many portfolios, mark watches or portfolio watches hold it. The meter is free during the beta; see Rate limits and credits. Add and remove requests accept at most 100 entries. The per-portfolio deadline cap above applies to both the JSON list and the calendar download, and holds even on plans with larger managed-marks allowances; exceeding it returns 422 portfolio_too_large. Split large portfolios; date/type filters do not reduce the mark count for this cap.

​
Membership references

When adding marks, use items to attach an optional external_ref to each membership. It is trimmed, 1–255 characters, case-sensitive, and unique within that portfolio. A trademark in two portfolios can carry a different reference in each. A reference can be attached to a membership that has none. Once bound, changing it or reusing it for another mark returns 409 external_ref_conflict; the whole add batch rolls back. Remove the membership and re-add it to bind a different reference. Look up a reference with Retrieve Portfolio using ?external_ref=..., or remove memberships by sending external_refs. Unknown references return an empty membership result or remove nothing. References cannot create placeholder marks outside Signa’s records.

​
Workflow

  1. Create a portfolio.
  2. Add trademark IDs and references.
  3. Retrieve its members or list computed deadlines.
  4. Optionally download a calendar file and import it into your calendar. The bearer-authenticated URL is a download; calendar subscriptions and automatic synchronization are unavailable.
Every POST, PATCH, and DELETE requires an Idempotency-Key. Retry the same target and body with the same key to replay the response for 24 hours. Reusing the key with a different target or body returns 409 conflict.

​
Get notified when a status changes

A portfolio is also what turns on direct change notifications: trademark.status_changed and office_action.issued are sent only for marks in at least one of your portfolios. When Signa corrects a status it published for one of these marks (for example a renewed mark shown as expired), you receive trademark.corrected on the same subscription, with no extra setup.
  1. Resolve office numbers to Signa IDs with Batch Trademarks: send up to 100 identifiers, each an application_number or registration_number with its office_code (for example {"application_number": "97123456", "office_code": "US"}), or an ir_number. Numbers Signa has no record for come back in not_found.
  2. Add the marks with items, putting your own matter number in external_ref.
  3. Create a webhook endpoint with enabled_events: ["trademark.status_changed", "office_action.issued"]. Set portfolio_id to receive only this portfolio’s marks.
  4. Each delivery carries trademark_id and a portfolios[] snapshot with your external_ref, so you can match it to your matter without another call. See payload shapes.
  5. Reconcile from the events feed on a schedule: GET /v1/events?sort=id&after=<last evt_ id>&portfolio_id=<ptf_ id>. Every delivery is also a row there, and some changes are recorded without a push (for example events from a bulk re-read of an office’s records, events that reach delivery more than 96 hours after Signa recorded them, or a single update that produces more than 5,000 events for your organization), so the feed is the complete record. It keeps 30 days; see Replay from a checkpoint.
Adding a mark does not replay its history, and an office action is sent only if it was issued in the last 90 days. Changes to other fields, such as the owner or an attorney, are not direct events. To receive them as alert.created, create a watch on the marks: mark for one mark, or the deprecated portfolio type for a set.