Working with Pentaleap Campaign and Reporting API

introduction pentaleap advertising technology powers leading retailers' retail media platforms with powerful retailer controls and our innovative fluid relevancy engine, pentaleap helps retailers, advertisers and customers get more from retail media we make our platform easy for partners to connect to pentaleap for various use cases such as unified campaign management and demand platforms set up campaigns, bids and optional targeting for your advertisers' products using our advertiser and campaign apis order management systems (oms) use our campaign, advertiser and publisher apis to centralise omnichannel media buying and reporting reporting, insight and billing/erp systems use our campaign and advertiser apis to understand campaign kpis and budget spent at a granular level custom uis our apis are ideal for retailers who want to stand up their own front end while having powerful and reliable apis behind it these apis power our own industry leading uis for both retailers and advertisers this documentation is designed for partners to create api connections with the pentaleap retail media platform it describes the api endpoints available, their specifications and their usage nb depending on the use case and partner type, access to some endpoints may be limited and permissions are granted on a case by case basis please discuss your needs with pentaleap directly to agree the most appropriate access level process for integrating with pentaleap get a testing account and access tokens from the pentaleap team please speak with your pentaleap contact directly (endpoints are provided in this guide for understanding and without host information) integrate and test the apis using the account and testing data provided by pentaleap to ensure that the integration is working as expected move to production and start working with the pentaleap retail media platform! special n otes on the api be aware that put api endpoints for updating an entity do not require sending the entire entitiy instead, partial updates of one or multiple fields are possible as well as a consequence, removing values of optional entity attributes require setting it explicitly to null e g { , "field"\ null, }