Partner Path

  1. Introduction call: Mutual information exchange, discuss use cases and pricing
  2. Kick off paperwork: Partner signs API evaluation agreement, MNDA, DPA
  3. Integration kick off call: Expand on partner’s ideal outcome, learn about Prism integration pathways (native or web), and partner’s use case. Develop integration architecture if not already defined by partner.
    1. Heads up before integration:
      1. Don’t use email as userToken (should be UUID)
      2. 3D Reconstruciton Pipeline
        1. Next Gen Web Scan Pipeline: assetConfigId == ee651a9e-6de1-4621-a5c9-5d31ca874718
        2. Next Gen Native Pipeline: assetConfigId == 25f6d3a6-a634-40c3-8452-0342bee242d0
        3. Legacy Native Pipeline: assetConfigId == c979ab6b-e46b-4c1c-89e1-bb02435b5cbf
      3. API Headers
        1. Content-Type: application/json
        2. Accept: application/json;v=1
  4. Begin integration

    1. Review documentation

      1. Notion, Githib, API docs, validation

      2. API Happy Path

        PrismAPI_HappyPath.png

    2. Body Fat Method

      1. When creating a new scan record, make sure you define the field bodyfatMethod
      2. We recommend using coco2 for all users. coco2 is our latest and most accurate body fat method. If you have a particularly muscular user base, reach out to Prism to discuss which body fat method is right for you

    3. Begin API and SDK integration

  5. Integration checkpoint: Review webhook documentation, consent screen requirements, pre scan education
  6. Pre-Launch Check: Has partner
    1. Signed contract?
    2. Migrated to prod?
    3. Finished prod webhooks?
    4. Passed consent screen approval?