As others said, no, there is no TPO in Scrum.
However, typically, companies employ the TPO role to bridge a gap. This gap is between one level up and one level down.
One level up and maybe you'll find the true PO, maybe it's someone from "The Business", or a collective of people who are shaping the product.
One level down, the problem is that the team needs to deliver technical tasks, as opposed to solutions. And the TPO typically creates "technical user stories" to be fed into the team.
I am a PO for system-to-system API's.
As you see the whole setup is around the technical aspect of the organization/product because if it weren't, the company wouldn't need a TPO in the first place. So they need this someone who can talk on a technical level with their surroundings. Sometimes, (I don't know whether that's the case with you) this role is just a renaming of a Project Manager role, who needs to have a technical view/opinion on the project. Thus, your role is restricted to the technical implementation side, rather than truly act as a customer.
Granted, this setup is caused by not having an actual product. It also goes hand in hand with component teams (as opposed to feature teams). Component teams are building just a part of the product/software e.g. the API, or the database, and therefore are "doomed" to work on technical tasks.