slug: splio provider: Splio generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 8 edges: - tag: Members spec_file: splio-members-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.92 evidence: POST /loyalty/members 'Create a member'; GET /loyalty/members/{id}/balance 'Get a member's point balance'; POST /loyalty/members/{card_code}/tier_change 'Update a member's tier' reason: Loyalty membership lifecycle, point balances and tier changes are core loyalty programme management, not generic customer master data. - tag: Programs spec_file: splio-programs-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.92 evidence: GET /loyalty/programs 'List programs'; GET /loyalty/programs/{id}/tiers 'List program's tiers' reason: Explicit loyalty programme and tier definitions plus programme membership listing — Loyalty & Retention Management. - tag: Points spec_file: splio-points-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.9 evidence: POST /loyalty/v1/members/{card_code}/credit 'Credit points' reason: Crediting and listing loyalty points for members is loyalty programme operation. - tag: Reward spec_file: splio-reward-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.9 evidence: POST /loyalty/v1/rewards/{id}/grant 'Grant a reward'; POST /loyalty/v1/reward-attributions/{id}/burn 'Use a reward granted to a loyalty member' reason: Reward definition, eligibility, granting and burning for loyalty members is loyalty programme administration. - tag: Loyalty spec_file: splio-loyalty-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.88 evidence: GET /loyalty/v2/contacts/{id}/points 'List a contact's points history' reason: Loyalty point history for a contact is squarely loyalty programme administration; vendor explicitly provides 'loyalty and rewards programs'. - tag: Reward stock and codes spec_file: splio-reward-stock-and-codes-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.82 evidence: POST /loyalty/rewards/{id}/instances/send 'Upload a reward's codes' reason: Loading redemption code inventory for loyalty rewards supports the loyalty/rewards programme; single operation so slightly lower confidence. - tag: Contact spec_file: splio-contact-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.8 evidence: GET /data/contacts List & search contacts; POST /data/contacts Create a contact; GET /data/contacts/{id}/activities; POST /data/contacts/optout reason: CRUD and search over the customer/contact record plus activities, orders, list subscriptions in a Customer Data Platform — customer master data management within CRM. - tag: Group spec_file: splio-group-api-openapi.yml capability_id: BC-420.20 capability_id_l1: BC-420 capability_name: Customer Segmentation Management confidence: 0.72 evidence: POST /target/groups 'Create a group'; POST /target/groups/{id}/add 'Add contacts to a group' reason: Groups of contacts created and maintained under the /target/ namespace are marketing audience segments/lists used for treatment targeting, matching Customer Segmentation Management. Some chance it is better read as generic customer data list handling.