the on_publish_receipt is a callback function defined in the MessagePublishReceiptListener class. You access this on the API level. You can think of Management vs Messaging APIs when using Solace as follows
Use the Management API for broker management such as setting configuration, creating resources, setting access rights…etc. Note that You have three ways to do this: CLI, SEMP API, Web based Gui. Step 3 in this codelab highlights the three main ways to manage configuration on the broker Event-Enable your REST Architecture with Solace PubSub+, Part 1 Use the Messaging API for all things messaging. So for example, if you want to interact with sending/receiving messages or checking on_publish_receipt for guaranteed messages. You can leverage any Solace messaging API or open standard protocols for this Using Guaranteed messaging For best practices, this is how we recommend implementing guaranteed messaging with Solace:
Create a queue on the broker Add topic subscriptions to it Publish on topics → queue will attract the message Consumer binds to queue Process the message on the consumer and explicitly send an acknowledgement after successful processing The message will be deleted from the queue when an acknowledgement is received Taking our Python API as an example, the publisher publishes messaged on a topic ( solace-samples-python/patterns/guaranteed_publisher.py at main · SolaceSamples/solace-samples-python · GitHub ) and the consumer binds to an existing queue on the broker ( https://github.com/SolaceSamples/solace-samples-python/blob/master/patterns/guaranteed_subscriber.py#L73-L76 )
Hands-on resources I recommend checking out our collection of codelabs on https://codelabs.solace.dev/ . There are a bunch of step by step tutorials to using different Solace features, integration guides, and use-cases examples.
Hopefully this helps! Let me know if you have any follow up questions 