> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stora.co/llms.txt
> Use this file to discover all available pages before exploring further.

# identity_verification.processing

> Triggered when an identity verification is processing



## OpenAPI

````yaml /2025-09/openapi.json webhook identity_verification.processing
openapi: 3.1.1
info:
  version: 2025-09
  title: Stora Public API
  description: >-
    The Stora Public API gives you programmatic access to your self-storage
    business. Use it to build custom integrations, automate operational
    workflows, and sync data with the tools you already use.
  termsOfService: https://www.stora.co/terms-of-service
  contact:
    name: Stora Support
    url: https://www.stora.co/contact
  x-build-date: '2025-02-22'
servers:
  - url: https://public-api.stora.co
    description: Production
security: []
tags:
  - name: Contacts
    description: >-
      Contact is the end user of an operator's storage business, an individual
      or company, used to manage everyone who inquires, books, signs contracts,
      and pays for storage. Use Staff instead for the operator's own team.
  - name: Contract Templates
    description: >-
      Contract Template is a reusable contract blueprint, used to generate
      contracts for a specific contact and tenancy. It contains the contract
      content with fillable fields and variables that Stora can pre-fill at
      document generation time.
  - name: Contracts
    description: >-
      Contract is a document generated from a contract template for a specific
      contact, used to track the signing lifecycle. It moves through statuses
      such as pending, signed, voided, declined, and deleted.
  - name: Coupons
    description: >-
      Coupon is a reusable promotion, used to reduce the price a contact pays by
      either a percentage or a fixed amount. It can be applied to eligible
      charges such as unit rent or products and may be limited by duration,
      number of uses, or scope. Use Price Adjustments instead to change an
      existing subscription's recurring price.
  - name: Credit Notes
    description: >-
      Credit Note is a document that reduces or reverses part or all of a
      previously issued invoice, used to correct what a contact was charged. It
      references the original invoice and contact, along with the specified
      corrected amounts and taxes.
  - name: Deals
    description: >-
      Deal is a qualified sales lead for a contact, used to track a potential
      rental through pipeline stages until it is won or lost. Use Opportunities
      instead to capture early interest before it is qualified, and Orders once
      the contact is ready to book with agreed pricing.
  - name: Deals / Stages
    description: >-
      Deal Stage is a step in the operator's sales pipeline, used to show how
      far a deal has progressed. Stages are configured in the Stora back office
      and are read-only through the API.
  - name: Identity Verifications
    description: >-
      Identity Verification is a check of a contact's identity documents, used
      to confirm who is renting before move-in. It records the verification's
      status, the reason it failed, and the contact it belongs to.
  - name: Images
    description: >-
      Image is a picture of a resource such as a site or unit type, used to
      display that resource in your own app or website. The endpoint redirects
      to a temporary pre-signed storage URL where the image can be downloaded.
  - name: Invoices
    description: >-
      Invoice is a finalized billing document issued to a contact, used to
      charge for their storage subscriptions and related charges. It itemizes
      line items like unit rent and protection, applies taxes and discounts, and
      tracks totals, balance due, and status over time.
  - name: Notes
    description: >-
      Note is a free-text annotation on a contact, unit, subscription, or task,
      used to record observations and context added by staff or integrations.
      Use Timeline Events instead to show structured activity from an external
      system on a resource's timeline.
  - name: OAuth 2
    description: >-
      OAuth 2 is the authorization standard of the Stora Public API, used to get
      the access token that authenticates every request. Use the **Client
      Credentials** flow if you are an operator building your own integration.
      Use the **Authorization Code** flow if you are a partner integrating on
      behalf of an operator.
  - name: Opportunities
    description: >-
      Opportunity is an expression of interest in storage, used to capture leads
      before they are qualified. Examples include an incomplete order, a price
      reveal, a quote request, or a lead captured before a site opens. Use Deals
      instead once the lead is qualified, and Orders once the contact is ready
      to book. It records the contact, the site and storage they were interested
      in, and can go on to be associated with a deal.
  - name: Orders
    description: >-
      Order is a contact's request to rent storage, used to book a unit type at
      a site with a move-in date and agreed pricing. Use Deals instead for leads
      that aren't ready to book. It includes optional add-ons like protection,
      products, and services and tracks status over its lifecycle. An order
      becomes `completed` when Stora creates its subscription and tenancy from
      it.
  - name: Orders / Line Items
    description: >-
      Order Line Item is an individual charge in an order, used to itemize what
      the contact will pay. Each line item represents a product or service such
      as unit rent, protection, or a one-off fee, and includes its quantity,
      unit price, and currency.
  - name: Price Adjustments
    description: >-
      Price Adjustment is a scheduled percentage change (increase or decrease)
      to a subscription's recurring prices, used to change what a contact pays
      from a future renewal date. It tracks its lifecycle from scheduling
      through application and invoicing, along with contact notification
      details. Use Coupons instead for promotional discounts.
  - name: Product Categories
    description: >-
      Product Category is a group of related products and services, used to
      classify them for pricing and display.
  - name: Products
    description: >-
      Product is a sellable item or service offered by the operator, used to
      sell extras alongside storage. It defines attributes such as name,
      description, pricing model, currency, and category, which determine how
      it's presented and billed. Use Protection Levels instead for coverage
      add-ons.
  - name: Protection Levels
    description: >-
      Protection Level is an optional add-on that protects a contact's stored
      goods up to a chosen coverage amount, used to offer coverage alongside
      storage. It's priced and billed alongside storage, appears as its own
      product or line item, and follows the same tax and discount rules as other
      charges.


      Each protection level belongs to one site. Global levels (`site` is
      `null`) stay readable for historical references, but you can't use them on
      new order or deal line items. See [Migrating to site-scoped protection
      levels](https://docs.stora.co/2025-09/guides/site-scoped-protection-levels).
  - name: Sites
    description: >-
      Site is a single physical self-storage location, used to scope units, unit
      types, pricing, and access control to that location. It's the container
      for everything specific to that location, including taxes and reporting.
  - name: Staff
    description: >-
      Staff is a member of the operator's team who uses the Stora back office,
      used to assign tasks and deals and to see who created a record.
  - name: Subscriptions
    description: >-
      Subscription is the recurring billing agreement for a contact's rental,
      used to charge them on a schedule for storage and related services. It
      defines the billing period and active prices, accrues charges into
      invoices, and reflects proration, discounts, and taxes. Use Tenancies
      instead for the physical side of the same rental.
  - name: Tasks
    description: >-
      Task is a to-do for staff, optionally linked to a unit, contact, or
      subscription, used to track follow-ups and operational work. Tasks are
      `open` or `completed` and can be assigned to a staff member.
  - name: Tenancies
    description: >-
      Tenancy is the storage agreement between a contact and the operator, used
      to see who rents which units at which site and for which dates. Use
      Subscriptions instead for the billing side of the same rental.
  - name: Timeline / Events
    description: >-
      Timeline Event is a custom entry from an external integration, used to
      show CRM, messaging, or other system activity on a resource's timeline.
      Use Notes instead for free-text annotations. An event can link to a
      contact, site, subscription, tenancy, unit, invoice, or unit type.
  - name: Timeline / Sources
    description: >-
      Timeline Source is the external system a timeline event comes from, such
      as a CRM or a custom integration, used to label and group events.
  - name: Timeline / Templates
    description: >-
      Timeline Template is the Liquid message format for a timeline event, used
      to render the event's text from its variables.
  - name: Unit Allocations
    description: >-
      Unit Allocation is the assignment of a specific unit to a tenancy, used to
      track when the unit was reserved and when the contact was granted access.
      Use Units instead for the unit's own details and status.
  - name: Unit Types
    description: >-
      Unit Type is a standardized storage offering at a site, such as "50 sq ft
      indoor" or "20 ft container", used to set pricing and show availability.
      It defines core attributes including size, features or access type, and
      display name.
  - name: Units
    description: >-
      Unit is a specific, bookable storage space at a site, for example "Unit
      A-012" of a given unit type, used to track each individual space and its
      status. Use Unit Allocations instead to see which tenancy a unit is
      assigned to.
  - name: Webhook Endpoints
    description: >-
      Webhook Endpoint is a URL you register with Stora, used to receive
      notifications when specific events occur. Use Webhooks instead for the
      event payloads Stora sends. Stora sends a `POST` request to the endpoint
      with the event payload.
  - name: Webhooks
    description: >-
      Webhook is an event notification that Stora sends as a `POST` request to
      your subscribed endpoints, used to react in real time when something
      happens, such as an invoice being paid. Use Webhook Endpoints instead to
      register the URLs that receive them. Stora sends each notification to all
      endpoints subscribed to that event type.
externalDocs:
  description: Stora Public API documentation website
  url: https://docs.stora.co/2025-09/
paths: {}

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.